neuron_update_contact
Update an existing contact's details. If notes are provided, they are appended as a new structured note entry without overwriting existing notes.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-contact.md
What neuron_update_contact does on Neuron
AI agents use neuron_update_contact 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 contact to update |
name | string | — | Updated full name for the contact |
tags | array | — | Updated tags for the contact (replaces existing tags) |
email | string | — | Updated email address for the contact |
notes | string | — | New note to append to the contact's existing notes |
phone | string | — | Updated phone number in E.164 format (e.g., +2348012345678) |
Parameters from the server's own tool schema.
Why neuron_update_contact is rated Medium
This tool modifies contact information in the platform's database, which is a Write operation. It does not delete data (thus not Destructive), does not execute code or commands (thus not Execute), and is not financial in nature.
From the tool's definition Tool description explicitly states 'Update an existing contact's details' and notes are 'appended as a new structured note entry' — these are reversible modification operations.
Attacks that exploit this kind of access
The rule that runs neuron_update_contact 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_contact, this is the rule to start with:
neuron_update_contact 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_contact call is checked against it from then on.
Questions about neuron_update_contact
Update an existing contact's details. If notes are provided, they are appended as a new structured note entry without overwriting existing notes. 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_contact accepts 6 parameters: id, name, tags, email, notes, phone. 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_contact: 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_contact 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_contact 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_contact. 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_contact 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