neuron_takeover_conversation
Transfer control of a conversation from the bot to a human agent. The bot will stop auto-responding until the conversation is released.
This record as markdown: /tools/io-github-conquext-neuron/neuron-takeover-conversation.md
What neuron_takeover_conversation does on Neuron
AI agents invoke neuron_takeover_conversation to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the conversation to take over |
Parameters from the server's own tool schema.
Why neuron_takeover_conversation is rated High
This tool triggers an external operational change — redirecting conversation handling from an automated bot to a human agent and halting bot auto-responses. It doesn't merely read or write data records, but executes a live workflow state change affecting ongoing conversations.
From the tool's definition Transfer control of a conversation from the bot to a human agent. The bot will stop auto-responding until the conversation is released.
Attacks that exploit this kind of access
The rule that runs neuron_takeover_conversation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_takeover_conversation, this is the rule to start with:
neuron_takeover_conversation stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_takeover_conversation call is checked against it from then on.
Questions about neuron_takeover_conversation
Transfer control of a conversation from the bot to a human agent. The bot will stop auto-responding until the conversation is released. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neuron_takeover_conversation accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_takeover_conversation: 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 Neuron. Nothing to install.
neuron_takeover_conversation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the neuron_takeover_conversation 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 neuron_takeover_conversation. 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.
neuron_takeover_conversation is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
Across the catalogue