neuron_update_organization
Update organization settings such as name, description, or configuration preferences. Only provided fields are changed.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-organization.md
What neuron_update_organization does on Neuron
AI agents use neuron_update_organization 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 | — | New display name for the organization |
orgId | string | Yes | Unique identifier (UUID) of the organization to update |
Parameters from the server's own tool schema.
Why neuron_update_organization is rated Medium
This tool modifies data (organization settings) but does so reversibly—changes to name, description, or configuration can be undone by updating again. It is not Destructive (no permanent deletion), not Execute (no code/command execution or triggering external operations), not Financial (no money movement), and not Read (it performs modifications, not just queries).
From the tool's definition Tool description states 'Update organization settings such as name, description, or configuration preferences.' The verb 'Update' and the reversible nature of modifying settings (name, description, configuration preferences) indicate this is a Write operation…
Attacks that exploit this kind of access
The rule that runs neuron_update_organization 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_organization, this is the rule to start with:
neuron_update_organization 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_organization call is checked against it from then on.
Questions about neuron_update_organization
Update organization settings such as name, description, or configuration preferences. Only provided fields are changed. 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_organization accepts 2 parameters: name, orgId. Required: orgId. 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_organization: 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_organization 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_organization 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_organization. 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_organization 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