Update the token metadata URI for an existing coin. Requires owner wallet.
AI agents use zora_update_coin_uri to create or update resources in Zora Coins MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zora Coins MCP Server environment.
This tool creates or modifies data reversibly by updating token metadata. While it requires authentication (owner wallet), an AI agent with access to the owner's credentials could misuse this to alter token properties, misleading users about the coin's attributes, contract details, or branding.
From the tool's definition The tool 'zora_update_coin_uri' modifies the token metadata URI for an existing coin, which is a reversible data mutation operation.
Attacks that exploit this kind of access
Update the token metadata URI for an existing coin. Requires owner wallet. It is categorised as a Write tool in the Zora Coins MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zora Coins MCP Server MCP server in PolicyLayer and add a rule for zora_update_coin_uri: 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_update_coin_uri is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zora_update_coin_uri 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_update_coin_uri. 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_update_coin_uri 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 →