neuron_bot_api_get_messages
Retrieve message history for a specific conversation with cursor-based pagination. Requires a valid API key.
This record as markdown: /tools/io-github-conquext-neuron/neuron-bot-api-get-messages.md
What neuron_bot_api_get_messages does on Neuron
AI agents call neuron_bot_api_get_messages 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 |
|---|---|---|---|
limit | number | — | Maximum number of messages to return (default: 50) |
apiKey | string | Yes | Bot API key with 'nrn_' prefix for authentication |
before | string | — | Cursor for pagination — retrieve messages created before this message ID or ISO 8601 timestamp |
conversationId | string | Yes | Unique identifier (UUID) of the conversation to retrieve messages from |
Parameters from the server's own tool schema.
Why neuron_bot_api_get_messages is rated Low
This tool retrieves existing message data via cursor-based pagination with no capability to modify, delete, or execute operations. The requirement for a valid API key is a standard authentication control. The blast radius of misuse is limited to unauthorized access to conversation history, which is a confidentiality concern but not execution, destruction, or financial risk.
From the tool's definition Tool name includes 'get_messages' and description states 'Retrieve message history' — both indicate data retrieval without modification or execution.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs neuron_bot_api_get_messages 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_get_messages, this is the rule to start with:
neuron_bot_api_get_messages 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_get_messages call is checked against it from then on.
Questions about neuron_bot_api_get_messages
Retrieve message history for a specific conversation with cursor-based pagination. 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_get_messages accepts 4 parameters: limit, apiKey, before, conversationId. Required: apiKey, conversationId. 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_get_messages: 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_get_messages 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_get_messages 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_get_messages. 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_get_messages 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