Prepare and store a read-only xgr-session-start@1 handoff for xDaLa Workbench. Use this tool whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session. Use this tool for starting an existing deployed XRC-729/XRC-137 workflow, starting from a runtime XRC-729 orches...
AI agents use create_xdala_session_start_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 prepares and stores a handoff object that initiates a blockchain session (XDaLa workflow). While described as 'read-only' in the sense that it stages/prepares rather than directly executing on-chain, it creates a persistent handoff artifact and is the precursor to launching on-chain sessions. The most severe applicable category is Write, as it creates/stores a handoff record.
From the tool's definition Prepare and store a read-only xgr-session-start@1 handoff... whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session
Attacks that exploit this kind of access
Prepare and store a read-only xgr-session-start@1 handoff for xDaLa Workbench. Use this tool whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session. Use this tool for starting an existing deployed XRC-729/XRC-137 workflow, starting from a runtime XRC-729 orchestration, starting from a bundle deploy result, or importing a canonical xgr-session-start@1 request into xDaLa Manage Sessions. When explaining required input to users, use canonical xgr-session-start@1 terminology: sessions[].orchestration, sessions[].ostcId, sessions[].stepId, sessions[].payload, sessions[].maxTotalGas. Do not ask users for entryStepId; entryStepId is not the Workbench Session Start field. For deployed XRC-729 workflows, first inspect the runtime, identify ostcId and the likely entry step, resolve that step\. 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_xdala_session_start_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_xdala_session_start_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_xdala_session_start_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_xdala_session_start_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_xdala_session_start_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 →