neuron_list_api_keys
Retrieve all API keys associated with a specific bot, including their names, creation dates, expiration status, and revocation status.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-api-keys.md
What neuron_list_api_keys does on Neuron
AI agents call neuron_list_api_keys 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 whose API keys to retrieve |
Parameters from the server's own tool schema.
Why neuron_list_api_keys is rated Low
This tool retrieves and queries existing API keys without modifying, deleting, or executing anything. However, severity is elevated to 'high' because API keys are sensitive credentials that, if exposed through misuse of this retrieval function, could enable unauthorized access to bot systems and third-party integrations.
From the tool's definition Tool name 'neuron_list_api_keys' and description 'Retrieve all API keys associated with a specific bot, including their names, creation dates, expiration status, and revocation status' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs neuron_list_api_keys 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_api_keys, this is the rule to start with:
neuron_list_api_keys 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_api_keys call is checked against it from then on.
Questions about neuron_list_api_keys
Retrieve all API keys associated with a specific bot, including their names, creation dates, expiration status, and revocation status. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_api_keys accepts 1 parameter: botId. 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_api_keys: 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_api_keys 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_api_keys 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_api_keys. 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_api_keys 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