Gets all supported ERC-20 tokens for a specific chain.
AI agents call get_supported_tokens 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 a list of supported tokens for a blockchain chain—purely informational data with no capability to modify, delete, execute code, or move funds. It is a straightforward read operation equivalent to querying a configuration or reference list. No reversible modifications, irreversible deletions, code execution, or financial transactions are possible through this tool.
From the tool's definition Tool name 'get_supported_tokens' and description 'Gets all supported ERC-20 tokens for a specific chain' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Gets all supported ERC-20 tokens for a specific chain. 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_tokens: 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_tokens 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_tokens 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_tokens. 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_tokens 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 →