Get all Chain IDs supported by Odos
AI agents call get_supported_chains 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.
This tool retrieves informational data about which blockchain networks are supported by the Odos service. It performs no write, destructive, financial, or execution operations. The blast radius of misuse is minimal—an agent calling this repeatedly or at scale would only result in redundant API calls, not unauthorized transactions, data loss, or financial harm.
From the tool's definition Tool name is 'get_supported_chains' and description states 'Get all Chain IDs supported by Odos'. The verb 'Get' and action of retrieving a static list of supported chain identifiers indicates a read-only query with no side effects or data modification.
Attacks that exploit this kind of access
Get all Chain IDs supported by Odos. 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_supported_chains: 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_supported_chains 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_supported_chains 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_supported_chains. 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_supported_chains 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 →