Deploy a new Zora coin. Requires PRIVATE_KEY; only Base mainnet is supported currently.
AI agents use zora_create_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.
Deploying a new coin on Base mainnet is a financial operation that commits on-chain resources, requires a private key to sign transactions, and involves real cryptocurrency expenditure (gas fees and potentially initial liquidity). The irreversible nature of blockchain deployment and the financial commitment involved make this a Financial/critical risk tool.
From the tool's definition Deploy a new Zora coin. Requires PRIVATE_KEY; only Base mainnet is supported currently.
Attacks that exploit this kind of access
Deploy a new Zora coin. Requires PRIVATE_KEY; only Base mainnet is supported currently. 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_create_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_create_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_create_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_create_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_create_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 →