Update an existing contact in CiviCRM including custom fields
AI agents use update_contact to create or update resources in CiviCRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CiviCRM MCP Server environment.
This tool modifies contact records reversibly by updating fields. It has medium blast radius: a misuse could corrupt contact data (addresses, phone numbers, email, custom fields) affecting customer/donor records, but changes are reversible via subsequent updates or version control.
From the tool's definition Tool description states 'Update an existing contact in CiviCRM including custom fields' — the verb 'update' directly indicates modification of existing data rather than retrieval (Read), deletion (Destructive), or code execution (Execute).
Attacks that exploit this kind of access
Update an existing contact in CiviCRM including custom fields. It is categorised as a Write tool in the CiviCRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for 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 CiviCRM MCP Server. Nothing to install.
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 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 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.
update_contact is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →