Returns metadata for a WASM code
AI agents call get-code-metadata 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 returns metadata about WASM code without modifying, executing, or deleting any data. It is a straightforward data lookup operation on the blockchain, analogous to a GET request in REST APIs. No state changes occur, no code execution is triggered, and no financial transactions are involved.
From the tool's definition Tool name 'get-code-metadata' and description 'Returns metadata for a WASM code' indicate a retrieval operation with no side effects. The verb 'Returns' and 'get' prefix are characteristic of read-only queries.
Attacks that exploit this kind of access
Returns metadata for a 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-code-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.
get-code-metadata 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-code-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 get-code-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.
get-code-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.
get-code-metadata is one line of Osmosis MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →