Validate a drafted XRC-137 authoring object.
AI agents call validate_xrc137_authoring 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 validation of a drafted object, which is a read-only operation that queries or checks data without modifying, executing, or deleting anything. It does not create, modify, delete, execute code, or move funds. The validation operation has no side effects on-chain or off-chain state.
From the tool's definition Tool name 'validate_xrc137_authoring' and description 'Validate a drafted XRC-137 authoring object' indicate a validation/checking operation with no side effects.
Attacks that exploit this kind of access
Validate a drafted XRC-137 authoring object. 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 validate_xrc137_authoring: 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.
validate_xrc137_authoring 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 validate_xrc137_authoring 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 validate_xrc137_authoring. 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.
validate_xrc137_authoring 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 →