neuron_add_tool_secret
Store or update a secret credential (API key, token, etc.) for a custom tool integration. Secrets are encrypted at rest.
This record as markdown: /tools/io-github-conquext-neuron/neuron-add-tool-secret.md
What neuron_add_tool_secret does on Neuron
AI agents use neuron_add_tool_secret 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 |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the tool to add the secret to |
key | string | Yes | Secret key name used in templates (e.g., 'API_KEY', 'AUTH_TOKEN') |
value | string | Yes | Secret value to store securely (will be encrypted) |
Parameters from the server's own tool schema.
Why neuron_add_tool_secret is rated Medium
This tool writes credentials/secrets to a secure storage system. While encrypted at rest, storing or updating secrets is a reversible write operation. However, given that the data involved is sensitive authentication material (API keys, tokens) that could be leveraged by an attacker if misused, the severity is high.
From the tool's definition "Store or update a secret credential (API key, token, etc.) for a custom tool integration. Secrets are encrypted at rest." - This tool creates or modifies stored secrets.
Attacks that exploit this kind of access
The rule that runs neuron_add_tool_secret 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_add_tool_secret, this is the rule to start with:
neuron_add_tool_secret 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_add_tool_secret call is checked against it from then on.
Questions about neuron_add_tool_secret
Store or update a secret credential (API key, token, etc.) for a custom tool integration. Secrets are encrypted at rest. 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_add_tool_secret accepts 3 parameters: id, key, value. Required: id, key, value. 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_add_tool_secret: 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_add_tool_secret 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_add_tool_secret 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_add_tool_secret. 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_add_tool_secret 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