neuron_update_kb_entry

Update the content, title, folder, or source of an existing knowledge base entry.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-update-kb-entry.md

WHAT IT DOES

What neuron_update_kb_entry does on Neuron

AI agents use neuron_update_kb_entry 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
`kbId`	string	Yes	Unique identifier of the knowledge base
`title`	string	—	New title for the entry
`folder`	string	—	New folder: 'general', 'skills', 'contexts', 'documents', or 'faqs'
`source`	string	—	New source type for the entry
`content`	string	—	New content for the entry
`entryId`	string	Yes	Unique identifier of the entry to update
`metadata`	object	—	New metadata key-value pairs

Parameters from the server's own tool schema.

RISK

Why neuron_update_kb_entry is rated Medium

This tool modifies existing data (knowledge base entries) but does not delete or destroy information—the changes can be reverted or re-edited. It is not Read (retrieves data only), Execute (runs external operations), Destructive (irreversibly deletes), or Financial.

From the tool's definition Tool name contains 'update' and description explicitly states 'Update the content, title, folder, or source of an existing knowledge base entry.' These are modifications to data that are reversible.

Risk signalsAccepts file system path (folder) · Accepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs neuron_update_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_update_kb_entry, this is the rule to start with:

neuron_update_kb_entry Rate-limited

neuron_update_kb_entry 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_update_kb_entry": {
      "limits": [
        {
          "counter": "neuron_update_kb_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_update_kb_entry call is checked against it from then on.

FAQ

Questions about neuron_update_kb_entry

What does the neuron_update_kb_entry tool do? +

Update the content, title, folder, or source of an existing knowledge base entry. 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.

What parameters does neuron_update_kb_entry accept? +

neuron_update_kb_entry accepts 7 parameters: kbId, title, folder, source, content, entryId, metadata. Required: kbId, entryId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_update_kb_entry? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_update_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.

What risk level is neuron_update_kb_entry? +

neuron_update_kb_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_update_kb_entry? +

Yes. Add a rate_limit block to the neuron_update_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.

How do I block neuron_update_kb_entry completely? +

Set action: deny in the PolicyLayer policy for neuron_update_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.

What MCP server provides neuron_update_kb_entry? +

neuron_update_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.

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 231 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →