Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range.
AI agents call list_xrc_events 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 retrieves historical event data with no side effects. It is purely a query operation that lists blockchain events based on filter criteria. Read-only operations that retrieve data have the lowest risk profile, making this a Read category tool with low severity.
From the tool's definition The tool is described as 'Read-only list of XRC events' with filtering capabilities (owner, contract, type/action, tx hash, block range). No modification, deletion, execution, or financial operations are mentioned.
Attacks that exploit this kind of access
Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range. 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 list_xrc_events: 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.
list_xrc_events 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 list_xrc_events 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 list_xrc_events. 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.
list_xrc_events 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 →