neuron_close_conversation
Close an active conversation, marking it as completed. The bot will stop responding and the conversation is archived.
This record as markdown: /tools/io-github-conquext-neuron/neuron-close-conversation.md
What neuron_close_conversation does on Neuron
AI agents use neuron_close_conversation to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the conversation to close |
Parameters from the server's own tool schema.
Why neuron_close_conversation is rated Medium
This tool modifies the state of a conversation by marking it as completed and archiving it. While the conversation data itself is not deleted (remains archived), the tool irreversibly changes the conversation's status and active state. This is a Write operation rather than Destructive because the data is preserved in archive form and the action is theoretically reversible (a conversation could be reopened).
From the tool's definition Close an active conversation, marking it as completed. The bot will stop responding and the conversation is archived.
Attacks that exploit this kind of access
The rule that runs neuron_close_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_close_conversation, this is the rule to start with:
neuron_close_conversation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_close_conversation call is checked against it from then on.
Questions about neuron_close_conversation
Close an active conversation, marking it as completed. The bot will stop responding and the conversation is archived. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_close_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_close_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_close_conversation 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 neuron_close_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_close_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_close_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.
This server
Across the catalogue