Returns all token factory denoms created by an address
AI agents call get-denoms-by-creator to retrieve information from Osmosis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (denoms created by an address) without modifying, deleting, or executing any state-changing operations. It is a straightforward read-only lookup on the blockchain, presenting minimal risk even if called by an AI agent with arbitrary arguments, as the worst case is returning data about token denoms the caller has created or querying public blockchain state.
From the tool's definition Tool name is 'get-denoms-by-creator' and description states it 'Returns all token factory denoms created by an address' — a pure query operation with no side effects.
Attacks that exploit this kind of access
Returns all token factory denoms created by an address. It is categorised as a Read tool in the Osmosis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for get-denoms-by-creator: 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.
get-denoms-by-creator is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-denoms-by-creator 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 get-denoms-by-creator. 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.
get-denoms-by-creator 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 →