Retrieve a concrete JSON example for XRC-137 or XRC-729.
AI agents call get_xgr_standard_example 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 is a straightforward data retrieval tool that returns reference examples for XRC standards. It has no side effects, does not execute code or transactions, and does not modify state. The verb 'retrieve' and the purpose (providing examples) confirm it is a Read operation with minimal security risk.
From the tool's definition The tool name 'get_xgr_standard_example' and description 'Retrieve a concrete JSON example for XRC-137 or XRC-729' indicate a retrieval operation that fetches example data for blockchain standards without modifying or executing any on-chain actions.
Attacks that exploit this kind of access
Retrieve a concrete JSON example for XRC-137 or XRC-729. 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_xgr_standard_example: 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_xgr_standard_example 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_xgr_standard_example 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_xgr_standard_example. 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_xgr_standard_example 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 →