Validate canonical deployable xgr-multi-bundle@1.
AI agents call validate_xgr_multibundle 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.
Validation is a read-only operation that checks properties or structure without triggering deployment, state changes, or financial transactions. The tool queries or inspects bundle data to confirm it meets requirements, which is consistent with Read category. Severity is low because validation has no side effects on chain state or user assets.
From the tool's definition Tool name 'validate_xgr_multibundle' and description 'Validate canonical deployable xgr-multi-bundle@1' indicate a validation/checking operation with no modification or execution of state.
Attacks that exploit this kind of access
Validate canonical deployable xgr-multi-bundle@1. 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_xgr_multibundle: 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_xgr_multibundle 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_xgr_multibundle 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_xgr_multibundle. 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_xgr_multibundle 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 →