neuron_approve_reflection
Approve a bot-generated reflection to incorporate the learned insight into the bot's future behavior and responses.
This record as markdown: /tools/io-github-conquext-neuron/neuron-approve-reflection.md
What neuron_approve_reflection does on Neuron
AI agents use neuron_approve_reflection 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 reflection to approve |
Parameters from the server's own tool schema.
Why neuron_approve_reflection is rated Medium
This tool creates or modifies data (the bot's learned behavior/responses) in a reversible manner. While it affects bot behavior, the change is configuration-based rather than destructive—the previous behavior can be reverted or the bot can be retrained.
From the tool's definition The tool 'approve a bot-generated reflection to incorporate the learned insight into the bot's future behavior and responses' modifies bot configuration or training state by persisting learned insights that will affect future responses.
Attacks that exploit this kind of access
The rule that runs neuron_approve_reflection 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_approve_reflection, this is the rule to start with:
neuron_approve_reflection 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_approve_reflection call is checked against it from then on.
Questions about neuron_approve_reflection
Approve a bot-generated reflection to incorporate the learned insight into the bot's future behavior and 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_approve_reflection 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_approve_reflection: 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_approve_reflection 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_approve_reflection 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_approve_reflection. 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_approve_reflection 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