Return a browser URL that opens the Add account flow for one integration. Use this for API keys/tokens so the user enters secrets directly in the web UI instead of sending them through the agent. Optionally preselect owner, auth template, and a non-secret label.
AI agents use connections.createHandoff to create or update resources in Executor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Executor environment.
This tool creates or registers a new account connection/handoff in the integration layer, which is a reversible data modification operation (Write category). It is not destructive since connections can be removed via the sibling connections.remove tool.
From the tool's definition The tool description states it 'Return[s] a browser URL that opens the Add account flow for one integration' and allows pre-selection of 'owner, auth template, and a non-secret label,' indicating it creates or initiates account connection configuration that…
Documented attack patterns abuse exactly the kind of access connections.createHandoff gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Executor, and nothing reaches the server without passing your rules. This is the rule we recommend for connections.createHandoff:
{
"version": "1",
"default": "deny",
"tools": {
"connections.createHandoff": {
"limits": [
{
"counter": "connections.createhandoff_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}connections.createHandoff 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.
Free to start. No card required.
Return a browser URL that opens the Add account flow for one integration. Use this for API keys/tokens so the user enters secrets directly in the web UI instead of sending them through the agent. Optionally preselect owner, auth template, and a non-secret label. It is categorised as a Write tool in the Executor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Executor MCP server in PolicyLayer and add a rule for connections.createHandoff: 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 Executor. Nothing to install.
connections.createHandoff 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 connections.createHandoff 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 connections.createHandoff. 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.
connections.createHandoff is provided by the Executor MCP server (rhyssullivan/executor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Executor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Executor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.