Swap ETH or ERC20 for a coin (or back). Uses permit2 for ERC20 where supported. Requires PRIVATE_KEY (EOA).
AI agents use zora_trade_coin to commit financial operations through Zora Coins MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool executes on-chain token trades involving real financial assets (ETH and ERC20 tokens) on Base mainnet. It moves money by swapping cryptocurrencies, which constitutes a financial transaction. Misuse could result in unauthorized trades, loss of funds, or draining of a wallet, making it critical severity.
From the tool's definition Swap ETH or ERC20 for a coin (or back). Requires PRIVATE_KEY (EOA).
Attacks that exploit this kind of access
Swap ETH or ERC20 for a coin (or back). Uses permit2 for ERC20 where supported. Requires PRIVATE_KEY (EOA). It is categorised as a Financial tool in the Zora Coins MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Zora Coins MCP Server MCP server in PolicyLayer and add a rule for zora_trade_coin: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Zora Coins MCP Server. Nothing to install.
zora_trade_coin is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the zora_trade_coin rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for zora_trade_coin. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
zora_trade_coin is provided by the Zora Coins MCP Server MCP server (r4topunk/zora-coins-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →