Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.
84
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Security
3 findings — 3 medium severity. This skill can be installed but you should review these findings before use.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 0.80). SKILL.md explicitly states that "When a server returns `402` the agent's payment tool automatically negotiates price, checks budget, signs a transaction, and retries," meaning the agent will ingest and act on arbitrary external HTTP responses (third‑party servers) which can materially change payment behavior.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Potentially malicious external URL detected (high risk: 0.90). The skill's MCP config and examples invoke "npx agentwallet-sdk@6.0.0" at runtime (a required dependency) which fetches and executes remote npm package code — see https://www.npmjs.com/package/agentwallet-sdk — so the external package controls executable behavior of the agent.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Direct money access detected (high risk: 1.00). The skill is explicitly a payments execution tool. It implements the x402 payment protocol, manages non-custodial wallets (ERC-4337), and exposes agent-callable tools such as send_payment (send payment to address/ENS), get_balance, and list_transactions. It signs transactions and can autonomously negotiate and retry payments when a 402 is returned. These are specific, purpose-built financial operations (wallet management and sending payments), not generic I/O or browsing capabilities.