Get all blockchain chains, optionally filtered by tag (Testnet, L2, or Beacon)
AI agents call get_chains to retrieve information from Chains API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries blockchain chain data with optional filters but does not modify, delete, execute code, or perform any financial operations. It is a standard Read operation with minimal risk—the worst-case misuse would be gathering information about blockchain chains, which poses no direct harm.
From the tool's definition Tool description explicitly states 'Get all blockchain chains' with optional filtering. The verb 'Get' and the read-only nature of querying chain metadata (chain details, RPC endpoints, relationships) without modification indicate a retrieval operation.
Attacks that exploit this kind of access
Get all blockchain chains, optionally filtered by tag (Testnet, L2, or Beacon). It is categorised as a Read tool in the Chains API MCP Server, which means it retrieves data without modifying state.
Register the Chains API MCP server in PolicyLayer and add a rule for 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 Chains API. Nothing to install.
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 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 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.
get_chains is provided by the Chains API MCP server (johnaverse/chains-api). 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 →