Get the operator status/incident page covering a specific chain by its chain ID (e.g. 8453 for Base → base-l2.statuspage.io).
AI agents call get_status_page_by_chain 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 performs a read-only operation that retrieves status page information for a blockchain chain. It accepts a chain ID parameter and returns publicly available status/incident data. There are no side effects, data modifications, or external state changes. The blast radius is minimal—misuse would result only in excessive queries to retrieve status information.
From the tool's definition Tool name contains 'get_' and description states 'Get the operator status/incident page'. The operation retrieves (queries) status page information by chain ID with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get the operator status/incident page covering a specific chain by its chain ID (e.g. 8453 for Base → base-l2.statuspage.io). 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_status_page_by_chain: 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_status_page_by_chain 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_status_page_by_chain 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_status_page_by_chain. 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_status_page_by_chain 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.
get_status_page_by_chain is one line of Chains API'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 →