neuron_delete_kb_entry
Permanently delete a specific entry from a knowledge base.
This record as markdown: /tools/io-github-conquext-neuron/neuron-delete-kb-entry.md
What neuron_delete_kb_entry does on Neuron
AI agents call neuron_delete_kb_entry to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
kbId | string | Yes | Unique identifier of the knowledge base |
entryId | string | Yes | Unique identifier of the entry to delete |
Parameters from the server's own tool schema.
Why neuron_delete_kb_entry is rated Critical
This tool performs an irreversible deletion operation on knowledge base data. Once a knowledge base entry is permanently deleted, it cannot be recovered. This fits the Destructive category definition: "irreversibly deletes or overwrites data, or actions that cannot be undone." The severity is high because unintended deletion of knowledge base entries could disrupt bot functionality, lose important training data, or…
From the tool's definition The tool description states it will "Permanently delete a specific entry from a knowledge base." The word "Permanently" combined with "delete" indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs neuron_delete_kb_entry 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_delete_kb_entry, this is the rule to start with:
neuron_delete_kb_entry is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_delete_kb_entry call is checked against it from then on.
Questions about neuron_delete_kb_entry
Permanently delete a specific entry from a knowledge base. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_delete_kb_entry accepts 2 parameters: kbId, entryId. Required: kbId, entryId. 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_delete_kb_entry: 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_delete_kb_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the neuron_delete_kb_entry 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_delete_kb_entry. 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_delete_kb_entry 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