neuron_detach_knowledge_base
Remove a knowledge base from a bot. The bot will no longer reference this knowledge base when generating responses.
This record as markdown: /tools/io-github-conquext-neuron/neuron-detach-knowledge-base.md
What neuron_detach_knowledge_base does on Neuron
AI agents use neuron_detach_knowledge_base 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 bot |
kbId | string | Yes | Unique identifier (UUID) of the knowledge base to detach |
Parameters from the server's own tool schema.
Why neuron_detach_knowledge_base is rated Medium
Detaching a knowledge base modifies the bot's configuration by removing an association, but it is likely reversible (the knowledge base itself is not deleted, and it can be re-attached). This fits the Write category. Misuse could degrade bot quality by removing its knowledge source, hence medium severity.
From the tool's definition Remove a knowledge base from a bot. The bot will no longer reference this knowledge base when generating responses.
Attacks that exploit this kind of access
The rule that runs neuron_detach_knowledge_base 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_detach_knowledge_base, this is the rule to start with:
neuron_detach_knowledge_base 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_detach_knowledge_base call is checked against it from then on.
Questions about neuron_detach_knowledge_base
Remove a knowledge base from a bot. The bot will no longer reference this knowledge base when generating responses. 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_detach_knowledge_base accepts 2 parameters: id, kbId. Required: id, kbId. 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_detach_knowledge_base: 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_detach_knowledge_base 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_detach_knowledge_base 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_detach_knowledge_base. 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_detach_knowledge_base 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