Get RPC, firehose, and substreams endpoints for a specific chain or all chains
AI agents call get_endpoints 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 blockchain endpoint data (RPC, firehose, substreams URLs) without any side effects, state changes, or code execution. It is purely informational and poses minimal risk even if misused by an AI agent, as it cannot modify data, execute operations, or access sensitive resources beyond public endpoint information.
From the tool's definition Tool description states 'Get RPC, firehose, and substreams endpoints' — this is a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get RPC, firehose, and substreams endpoints for a specific chain or all chains. 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_endpoints: 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_endpoints 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_endpoints 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_endpoints. 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_endpoints 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 →