Returns all contracts instantiated from a specific code ID
AI agents call get-contracts-by-code 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 is a read-only query tool that retrieves contract information from the blockchain based on a code ID parameter. It performs no state changes, financial transactions, or destructive operations. The 'Returns' verb and lack of action descriptors confirm this is a data retrieval operation, placing it in the Read category with low severity.
From the tool's definition Tool name 'get-contracts-by-code' and description 'Returns all contracts instantiated from a specific code ID' indicate a query operation that retrieves and lists data without modification or side effects.
Attacks that exploit this kind of access
Returns all contracts instantiated from a specific code ID. 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-contracts-by-code: 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-contracts-by-code 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-contracts-by-code 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-contracts-by-code. 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-contracts-by-code 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 →