Alias for validate_xgr_multibundle.
AI agents call validate_xdala_bundle 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 tools inspect data for correctness or compliance without modifying state. The tool performs a read-only assessment of a bundle's validity. While the description lacks detail about validate_xgr_multibundle, the validation semantic and the server's emphasis on queries and preparation (not execution/completion) strongly suggest a Read operation.
From the tool's definition Tool name 'validate_xdala_bundle' and alias reference 'validate_xgr_multibundle' indicate a validation/check operation. The server description emphasizes 'queries' and 'preparing' actions, with no mutation language.
Attacks that exploit this kind of access
Alias for validate_xgr_multibundle. 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_xdala_bundle: 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_xdala_bundle 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_xdala_bundle 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_xdala_bundle. 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_xdala_bundle 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 →