Returns information about a specific WASM code
AI agents call get-wasm-code-info 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 queries and returns data about WASM code without modifying, executing, or deleting anything. It is a straightforward read operation on blockchain state, consistent with information retrieval tools like 'get' or 'fetch'. The low severity reflects minimal blast radius; misuse would only result in unwanted information disclosure.
From the tool's definition Tool name is 'get-wasm-code-info' and description states 'Returns information about a specific WASM code' — clearly a retrieval operation with no side effects.
Attacks that exploit this kind of access
Returns information about a specific WASM code. 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-wasm-code-info: 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-wasm-code-info 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-wasm-code-info 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-wasm-code-info. 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-wasm-code-info 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 →