neuron_toggle_builtin_tool
Toggle a built-in tool on or off for a specific bot. Enabled tools become available in the bot's conversations. Example tool IDs: delete_message, post_to_channel, post_status, web_search, send_direct_message, react_to_message, set_reminder, create_poll.
This record as markdown: /tools/io-github-conquext-neuron/neuron-toggle-builtin-tool.md
What neuron_toggle_builtin_tool does on Neuron
AI agents use neuron_toggle_builtin_tool 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 |
|---|---|---|---|
botId | string | Yes | Unique identifier (UUID) of the bot to toggle the tool for |
toolId | string | Yes | Identifier of the built-in tool (e.g., 'delete_message', 'post_status', 'web_search') |
enabled | boolean | Yes | Whether to enable (true) or disable (false) the tool |
Parameters from the server's own tool schema.
Why neuron_toggle_builtin_tool is rated Medium
This tool modifies the configuration of a bot by enabling or disabling built-in tools. It is a reversible state change (toggling on/off), making it a Write operation. However, the severity is medium because enabling certain tools (e.g., delete_message, post_to_channel, send_direct_message) could indirectly allow harmful actions if misused — but the toggle itself is reversible.
From the tool's definition Toggle a built-in tool on or off for a specific bot. Enabled tools become available in the bot's conversations.
Attacks that exploit this kind of access
The rule that runs neuron_toggle_builtin_tool 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_toggle_builtin_tool, this is the rule to start with:
neuron_toggle_builtin_tool 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_toggle_builtin_tool call is checked against it from then on.
Questions about neuron_toggle_builtin_tool
Toggle a built-in tool on or off for a specific bot. Enabled tools become available in the bot's conversations. Example tool IDs: delete_message, post_to_channel, post_status, web_search, send_direct_message, react_to_message, set_reminder, create_poll. 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_toggle_builtin_tool accepts 3 parameters: botId, toolId, enabled. Required: botId, toolId, enabled. 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_toggle_builtin_tool: 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_toggle_builtin_tool 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_toggle_builtin_tool 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_toggle_builtin_tool. 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_toggle_builtin_tool 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