neuron_pause_bot
Pause a bot to temporarily stop it from processing new messages. The bot retains its configuration and can be resumed later.
This record as markdown: /tools/io-github-conquext-neuron/neuron-pause-bot.md
What neuron_pause_bot does on Neuron
AI agents invoke neuron_pause_bot 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 bot to pause |
Parameters from the server's own tool schema.
Why neuron_pause_bot is rated High
This tool triggers an operational state change on an external service (stopping a bot from processing messages). It is reversible (can be resumed later), so it does not qualify as Destructive. It does not merely read or write data — it executes a control action that affects the bot's runtime behavior, making Execute the most appropriate category.
From the tool's definition Pause a bot to temporarily stop it from processing new messages
Attacks that exploit this kind of access
The rule that runs neuron_pause_bot 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_pause_bot, this is the rule to start with:
neuron_pause_bot 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_pause_bot call is checked against it from then on.
Questions about neuron_pause_bot
Pause a bot to temporarily stop it from processing new messages. The bot retains its configuration and can be resumed later. 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_pause_bot 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_pause_bot: 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_pause_bot 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_pause_bot 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_pause_bot. 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_pause_bot 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