cancel_xdala_bundle_deploy_handoff

Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.

Server XGR MCP Gateway xgr-network/xgr-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What cancel_xdala_bundle_deploy_handoff does on XGR MCP Gateway

AI agents call cancel_xdala_bundle_deploy_handoff to permanently remove resources in XGR MCP Gateway — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why cancel_xdala_bundle_deploy_handoff needs a policy

Cancelling a handoff irreversibly removes/voids a pending operation. Although the description clarifies it is 'offchain metadata only and never cancels chain transactions,' the act of cancelling a pending handoff cannot be undone — the handoff record is permanently voided. This makes it Destructive rather than Write, though the blast radius is limited to offchain metadata (medium severity).

From the tool's definition Cancel a pending XDaLa bundle deploy handoff

Questions about cancel_xdala_bundle_deploy_handoff

What does the cancel_xdala_bundle_deploy_handoff tool do? +

Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions. It is categorised as a Destructive tool in the XGR MCP Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_xdala_bundle_deploy_handoff? +

Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for cancel_xdala_bundle_deploy_handoff: 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.

What risk level is cancel_xdala_bundle_deploy_handoff? +

cancel_xdala_bundle_deploy_handoff is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_xdala_bundle_deploy_handoff? +

Yes. Add a rate_limit block to the cancel_xdala_bundle_deploy_handoff 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.

How do I block cancel_xdala_bundle_deploy_handoff completely? +

Set action: deny in the PolicyLayer policy for cancel_xdala_bundle_deploy_handoff. 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.

What MCP server provides cancel_xdala_bundle_deploy_handoff? +

cancel_xdala_bundle_deploy_handoff 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.