get_contract_info
AI agents call get_contract_info to retrieve information from Odos MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and pattern of sibling tools all performing data retrieval without modification strongly suggests this is a read operation that queries blockchain contract metadata. No write, execute, destructive, or financial operations are indicated. Confidence is slightly reduced due to empty description, but context and naming convention are clear indicators of a read-only function.
From the tool's definition Tool name 'get_contract_info' indicates retrieval of contract information. Description is empty, but context shows this server provides blockchain data access alongside similar read-only tools like 'get_chain_token_prices', 'get_currencies',…
Attacks that exploit this kind of access
get_contract_info. It is categorised as a Read tool in the Odos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odos MCP Server MCP server in PolicyLayer and add a rule for get_contract_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 Odos MCP Server. Nothing to install.
get_contract_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_contract_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_contract_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_contract_info is provided by the Odos MCP Server MCP server (odos-xyz/odos-mcp). 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 →