neuron_list_reflections
Retrieve pending reflections that the bot has generated from conversations, awaiting human review. Optionally filter by approval status.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-reflections.md
What neuron_list_reflections does on Neuron
AI agents call neuron_list_reflections to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
botId | string | Yes | Unique identifier (UUID) of the bot to list reflections for |
status | string | — | Filter reflections by approval status (default: all statuses) |
Parameters from the server's own tool schema.
Why neuron_list_reflections is rated Low
This tool retrieves and lists existing data (pending reflections) without side effects. It matches the 'Read' category definition: retrieves or queries data with no side effects. The severity is low because accessing reflection metadata poses minimal risk; the data retrieved appears to be internal bot-generated content for administrative purposes, not sensitive user information or financial data.
From the tool's definition Tool name and description indicate 'Retrieve pending reflections' with optional filtering. No modification, deletion, or execution of external operations occurs—purely a query operation to list data awaiting review.
Attacks that exploit this kind of access
The rule that runs neuron_list_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_list_reflections, this is the rule to start with:
neuron_list_reflections is read-only, so it stays allowed. 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_list_reflections call is checked against it from then on.
Questions about neuron_list_reflections
Retrieve pending reflections that the bot has generated from conversations, awaiting human review. Optionally filter by approval status. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_reflections accepts 2 parameters: botId, status. 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_list_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_list_reflections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_list_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_list_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_list_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