Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters.
AI agents call get_xrc_failure_stats to retrieve information from XGR MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only, querying statistics about XRC-137 rules and XRC-729 filters without side effects. The 'Read-only' designation and statistical query nature confirm it belongs in the Read category. Low severity reflects minimal risk from misuse—an agent retrieving blockchain statistics poses negligible harm compared to tools that execute, modify, or delete data.
From the tool's definition Tool description explicitly states 'Read-only' and retrieves 'invalid/failure statistics' with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for get_xrc_failure_stats: 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 XGR MCP Gateway. Nothing to install.
get_xrc_failure_stats 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_xrc_failure_stats 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_xrc_failure_stats. 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_xrc_failure_stats is provided by the XGR MCP Gateway MCP server (xgr-network/xgr-mcp). 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 →