Create an offchain human-in-the-loop operation and return a browser URL. The MCP never signs or submits transactions; the user executes locally with a browser wallet on the operation page. Do not use this tool to start, run, launch, execute, or queue XDaLa sessions. Do not use this tool for xgr_v...
AI agents use create_operation_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.
This tool creates a handoff operation (a Write action) that prepares an on-chain transaction for human approval via a browser wallet. While the MCP itself does not sign or submit, it creates a persistent offchain operation record and generates a URL, which constitutes a reversible write.
From the tool's definition 'Create an offchain human-in-the-loop operation and return a browser URL' and 'The MCP never signs or submits transactions; the user executes locally with a browser wallet on the operation page'
Attacks that exploit this kind of access
Create an offchain human-in-the-loop operation and return a browser URL. The MCP never signs or submits transactions; the user executes locally with a browser wallet on the operation page. Do not use this tool to start, run, launch, execute, or queue XDaLa sessions. Do not use this tool for xgr_validateDataTransfer, SessionPermit, Manage Sessions imports, xgr-session-start@1, XDaLa session start handoffs, or starting a deployed XRC-729 workflow. For these intents, use create_xdala_session_start_handoff. If create_xdala_session_start_handoff is unavailable, report that the session-start tool is unavailable instead of falling back to create_operation_handoff. 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.
Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for create_operation_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.
create_operation_handoff is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_operation_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.
Set action: deny in the PolicyLayer policy for create_operation_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.
create_operation_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.
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 →