neuron_bot_api_get_bot
Retrieve configuration and status information about the bot associated with the provided API key.
This record as markdown: /tools/io-github-conquext-neuron/neuron-bot-api-get-bot.md
What neuron_bot_api_get_bot does on Neuron
AI agents call neuron_bot_api_get_bot 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 |
|---|---|---|---|
apiKey | string | Yes | Bot API key with 'nrn_' prefix for authentication |
Parameters from the server's own tool schema.
Why neuron_bot_api_get_bot is rated Low
The tool performs a read-only operation to fetch bot configuration and status metadata. There are no side effects, no data modifications, no code execution, and no irreversible actions. The severity is low because retrieving bot configuration information has minimal blast radius even if accessed without authorization - it's informational data without operational impact.
From the tool's definition Tool name and description: 'Retrieve configuration and status information about the bot' - this is a query/get operation that retrieves data without modifying or executing anything.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs neuron_bot_api_get_bot 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_bot, this is the rule to start with:
neuron_bot_api_get_bot 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_bot call is checked against it from then on.
Questions about neuron_bot_api_get_bot
Retrieve configuration and status information about the bot associated with the provided 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_bot accepts 1 parameter: apiKey. 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_get_bot: 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_bot 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_bot 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_bot. 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_bot 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