neuron_create_api_key
Create a new API key for programmatic access to a specific bot. Store the key securely as it cannot be retrieved later.
This record as markdown: /tools/io-github-conquext-neuron/neuron-create-api-key.md
What neuron_create_api_key does on Neuron
AI agents use neuron_create_api_key to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Descriptive name for the API key to identify its purpose (e.g., 'Production CRM Integration') |
botId | string | Yes | Unique identifier (UUID) of the bot to create the API key for |
expiresAt | string | — | ISO 8601 date-time when the key should expire (e.g., '2026-12-31T23:59:59Z'). Key never expires if omitted. |
Parameters from the server's own tool schema.
Why neuron_create_api_key is rated Medium
This tool creates a new credential (API key) that grants programmatic access to a bot. This is a Write operation as it creates a new, persistent authentication credential. Severity is high because a compromised API key could allow unauthorized access to bot functionality, potentially enabling attackers to send messages, modify bot behavior, or access sensitive data associated with the bot.
From the tool's definition Create a new API key for programmatic access to a specific bot. Store the key securely as it cannot be retrieved later.
Attacks that exploit this kind of access
The rule that runs neuron_create_api_key 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_create_api_key, this is the rule to start with:
neuron_create_api_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_api_key call is checked against it from then on.
Questions about neuron_create_api_key
Create a new API key for programmatic access to a specific bot. Store the key securely as it cannot be retrieved later. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_create_api_key accepts 3 parameters: name, botId, expiresAt. Required: name, 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_create_api_key: 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_create_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the neuron_create_api_key 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_create_api_key. 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_create_api_key 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