neuron_sync_knowledge
Trigger a synchronization operation to refresh embeddings, reindex content, or update the knowledge base state.
This record as markdown: /tools/io-github-conquext-neuron/neuron-sync-knowledge.md
What neuron_sync_knowledge does on Neuron
AI agents invoke neuron_sync_knowledge 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 of the knowledge base to synchronize |
Parameters from the server's own tool schema.
Why neuron_sync_knowledge is rated High
This tool executes a backend process (synchronization, embedding refresh, reindexing) rather than simply reading or writing discrete data. While not destructive (the operation is reversible and doesn't permanently delete data), it triggers external operations whose consequences depend on system state.
From the tool's definition Trigger a synchronization operation to refresh embeddings, reindex content, or update the knowledge base state.
Attacks that exploit this kind of access
The rule that runs neuron_sync_knowledge 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_sync_knowledge, this is the rule to start with:
neuron_sync_knowledge 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_sync_knowledge call is checked against it from then on.
Questions about neuron_sync_knowledge
Trigger a synchronization operation to refresh embeddings, reindex content, or update the knowledge base state. 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_sync_knowledge 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_sync_knowledge: 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_sync_knowledge 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_sync_knowledge 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_sync_knowledge. 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_sync_knowledge 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