neuron_sync_reflections
Synchronize all approved reflections into the bot's active knowledge base, applying learned insights to future conversations.
This record as markdown: /tools/io-github-conquext-neuron/neuron-sync-reflections.md
What neuron_sync_reflections does on Neuron
AI agents use neuron_sync_reflections 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 sync reflections for |
Parameters from the server's own tool schema.
Why neuron_sync_reflections is rated Medium
This tool modifies bot configuration by integrating reflections into the knowledge base, which is a reversible write operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial operations.
From the tool's definition Tool name 'sync_reflections' and description 'Synchronize all approved reflections into the bot's active knowledge base' indicates modification of the bot's knowledge base state.
Attacks that exploit this kind of access
The rule that runs neuron_sync_reflections 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_reflections, this is the rule to start with:
neuron_sync_reflections 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_sync_reflections call is checked against it from then on.
Questions about neuron_sync_reflections
Synchronize all approved reflections into the bot's active knowledge base, applying learned insights to future conversations. 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_sync_reflections accepts 1 parameter: botId. Required: botId. 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_reflections: 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_reflections 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_sync_reflections 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_reflections. 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_reflections 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