Get RPC monitor status and summary endpoint health counts across all chains (without per-chain endpoint listing)
AI agents call get_rpc_monitor 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 monitoring status and health metrics about RPC endpoints across blockchain chains. It performs no mutations, deletions, or executable operations — it only queries and returns summary data. The read-only nature and lack of side effects place it squarely in the Read category with low severity, as misuse would only expose informational data about infrastructure health.
From the tool's definition Tool name 'get_rpc_monitor' and description explicitly state it 'Get[s] RPC monitor status and summary endpoint health counts' — pure data retrieval with 'no per-chain endpoint listing', indicating a query-only operation.
Attacks that exploit this kind of access
Get RPC monitor status and summary endpoint health counts across all chains (without per-chain endpoint listing). 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_rpc_monitor: 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_rpc_monitor 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_rpc_monitor 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_rpc_monitor. 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_rpc_monitor 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 →