Get all supported chains for cross-chain operations. Returns detailed information about each chain including RPC URLs, explorers, currencies, and supported tokens.\n\nCommon Chain IDs:\n• Ethereum: 1\n• Optimism: 10\n• Polygon: 137\n• Arbitrum: 42161\n• Base: 8453\n• BNB Chain: 56\n\nOptional: Us...
AI agents call relay_get_chains to retrieve information from Relay Protocol 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 enumerates configuration data (chain metadata, RPC URLs, explorers, currencies, supported tokens) without modifying state, executing code, or committing any financial transactions. It is a pure data retrieval endpoint. While the underlying blockchain system is financial in nature, this tool itself only reads static or cached chain information.
From the tool's definition Tool description explicitly states 'Get all supported chains' and 'Returns detailed information about each chain' — this is a query/lookup operation with no side effects.
Attacks that exploit this kind of access
Get all supported chains for cross-chain operations. Returns detailed information about each chain including RPC URLs, explorers, currencies, and supported tokens.\n\nCommon Chain IDs:\n• Ethereum: 1\n• Optimism: 10\n• Polygon: 137\n• Arbitrum: 42161\n• Base: 8453\n• BNB Chain: 56\n\nOptional: Use includeChains parameter to filter specific chains (comma-separated chain IDs). It is categorised as a Read tool in the Relay Protocol MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay Protocol MCP Server MCP server in PolicyLayer and add a rule for relay_get_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 Relay Protocol MCP Server. Nothing to install.
relay_get_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 relay_get_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 relay_get_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.
relay_get_chains is provided by the Relay Protocol MCP Server MCP server (warengonzaga/relay-protocol-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
relay_get_chains is one line of Relay Protocol 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 →