create_xdala_bundle_deploy_handoff · XGR MCP Gateway MCP

WHAT IT DOES

What create_xdala_bundle_deploy_handoff does on XGR MCP Gateway

AI agents use create_xdala_bundle_deploy_handoff to create or update resources in XGR MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XGR MCP Gateway environment.

WHY IT NEEDS A POLICY

Why create_xdala_bundle_deploy_handoff needs a policy

This tool stores bundle configuration data offchain and generates a reference handle for later retrieval/execution. While it relates to blockchain operations, it only creates/persists data without actually executing transactions or moving funds. The blast radius is limited to accidental creation of unintended bundle deployments that would require additional user action to execute.

From the tool's definition Tool description explicitly states 'Store a validated xgr-multi-bundle@1 bundle offchain under an unguessable bearer handle' — this creates and persists data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_xdala_bundle_deploy_handoff Rate-limited

create_xdala_bundle_deploy_handoff stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_xdala_bundle_deploy_handoff": {
      "limits": [
        {
          "counter": "create_xdala_bundle_deploy_handoff_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches XGR MCP Gateway, so you can run agents against it safely.

FAQ

Questions about create_xdala_bundle_deploy_handoff

What does the create_xdala_bundle_deploy_handoff tool do? +

Store a validated xgr-multi-bundle@1 bundle offchain under an unguessable bearer handle and return an XDaLa Workbench import URL. The MCP does not sign, submit, or execute transactions. It is categorised as a Write tool in the XGR MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_xdala_bundle_deploy_handoff? +

Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for create_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 create_xdala_bundle_deploy_handoff? +

create_xdala_bundle_deploy_handoff is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_xdala_bundle_deploy_handoff? +

Yes. Add a rate_limit block to the create_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 create_xdala_bundle_deploy_handoff completely? +

Set action: deny in the PolicyLayer policy for create_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 create_xdala_bundle_deploy_handoff? +

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