Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner.
AI agents call get_xrc_owner_summary 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 data without creating, modifying, deleting, or executing operations. The explicit 'read-only' designation confirms it has no side effects. Severity is low because information disclosure about blockchain assets, while sensitive, does not directly enable unauthorized state changes or financial harm on its own.
From the tool's definition Tool name contains 'get_' and description explicitly states 'read-only summary' with no mutation or side effects. It retrieves 'assets and recent XRC events for an owner'—purely informational queries.
Attacks that exploit this kind of access
Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner. 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_owner_summary: 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_owner_summary 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_owner_summary 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_owner_summary. 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_owner_summary 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 →