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.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 81 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-update-contact.md

WHAT IT DOES

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)
`doNotBroadcast`	boolean	—	Set true to exclude this contact from all broadcasts, false to allow
`doNotAutoRespond`	boolean	—	Set true so the bot never auto-responds to this contact, false to allow (manual/API and human sends are unaffected either way)

Parameters from the server's own tool schema.

RISK

Why neuron_update_contact is rated Medium

An AI agent can call neuron_update_contact 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_update_contact": {
      "limits": [
        {
          "counter": "neuron_update_contact_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about neuron_update_contact

What does the neuron_update_contact tool do? +

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.

What parameters does neuron_update_contact accept? +

neuron_update_contact accepts 8 parameters: id, name, tags, email, notes, phone, doNotBroadcast, doNotAutoRespond. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_update_contact? +

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.

What risk level is neuron_update_contact? +

neuron_update_contact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_update_contact? +

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.

How do I block neuron_update_contact completely? +

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.

What MCP server provides neuron_update_contact? +

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.

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 281 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →