Set metadata for a token factory token
AI agents use set-token-metadata to create or update resources in Osmosis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Osmosis MCP Server environment.
This tool creates or modifies token metadata, which is a reversible write operation. While not destructive (data can be updated again) or financial in itself, it affects token properties on a blockchain and could have significant consequences if misapplied (e.g., setting misleading metadata).
From the tool's definition The tool 'set-token-metadata' modifies token metadata on the Osmosis blockchain, which is a write operation that changes data state.
Attacks that exploit this kind of access
Set metadata for a token factory token. It is categorised as a Write tool in the Osmosis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for set-token-metadata: 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 Osmosis MCP Server. Nothing to install.
set-token-metadata 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 set-token-metadata 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 set-token-metadata. 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.
set-token-metadata is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). 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 →