neuron_update_tool
Modify an existing custom API tool's configuration, including its endpoint, authentication, or request template.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-tool.md
What neuron_update_tool does on Neuron
AI agents use neuron_update_tool 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 update |
name | string | — | Updated human-readable name for the tool |
type | string | — | Updated type of the tool integration |
config | object | — | Updated tool configuration |
authType | string | — | Updated authentication type |
rateLimit | number | — | Updated maximum requests per minute |
timeoutMs | number | — | Updated request timeout in milliseconds |
description | string | — | Updated description of the tool's purpose |
Parameters from the server's own tool schema.
Why neuron_update_tool is rated Medium
An AI agent can call neuron_update_tool faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (config.endpoint) · High parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs neuron_update_tool 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_update_tool, this is the rule to start with:
neuron_update_tool 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_update_tool call is checked against it from then on.
Questions about neuron_update_tool
Modify an existing custom API tool's configuration, including its endpoint, authentication, or request template. 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_update_tool accepts 8 parameters: id, name, type, config, authType, rateLimit, timeoutMs, description. Required: id. 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_update_tool: 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_update_tool 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_update_tool 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_update_tool. 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_update_tool 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