Returns the source information for an IBC token
AI agents call get-ibc-denom-trace 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 blockchain data (IBC token source information) with no side effects. It is a read-only query operation that does not execute transactions, modify state, or move funds. The 'get-' prefix and 'returns' verb confirm retrieval semantics. Low severity because misuse would only expose informational data about token origins.
From the tool's definition Tool name 'get-ibc-denom-trace' and description 'Returns the source information for an IBC token' indicate a query operation that retrieves data without modification or execution of transactions.
Attacks that exploit this kind of access
Returns the source information for an IBC token. 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-ibc-denom-trace: 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-ibc-denom-trace 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-ibc-denom-trace 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-ibc-denom-trace. 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-ibc-denom-trace 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 →