neuron_bot_api_list_conversations
Retrieve a paginated list of conversations managed by the bot. Supports filtering by conversation status. Requires a valid API key.
This record as markdown: /tools/io-github-conquext-neuron/neuron-bot-api-list-conversations.md
What neuron_bot_api_list_conversations does on Neuron
AI agents call neuron_bot_api_list_conversations 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 |
|---|---|---|---|
page | number | — | Page number for pagination (default: 1) |
limit | number | — | Number of conversations per page (default: 20) |
apiKey | string | Yes | Bot API key with 'nrn_' prefix for authentication |
status | string | — | Filter by conversation status: 'active', 'closed', or 'pending' |
Parameters from the server's own tool schema.
Why neuron_bot_api_list_conversations is rated Low
This is a straightforward data retrieval operation that queries existing conversation records without side effects. The tool supports filtering and pagination but does not create, modify, delete, or execute any actions.
From the tool's definition Tool retrieves ("Retrieve") a paginated list of conversations with filtering capabilities. No modification, deletion, or execution of external operations is described.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs neuron_bot_api_list_conversations 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_bot_api_list_conversations, this is the rule to start with:
neuron_bot_api_list_conversations 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_bot_api_list_conversations call is checked against it from then on.
Questions about neuron_bot_api_list_conversations
Retrieve a paginated list of conversations managed by the bot. Supports filtering by conversation status. Requires a valid API key. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_bot_api_list_conversations accepts 4 parameters: page, limit, apiKey, status. Required: apiKey. 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_bot_api_list_conversations: 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_bot_api_list_conversations 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_bot_api_list_conversations 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_bot_api_list_conversations. 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_bot_api_list_conversations 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