Update an existing address record
AI agents use update_address 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 existing address data without deleting it, which is a Write operation. It is reversible (the address can be updated again to restore previous values), so it is not Destructive. Severity is medium because incorrect address updates could affect contact management and communication routing, but the blast radius is limited to a single address record and the operation is recoverable.
From the tool's definition Tool name 'update_address' and description 'Update an existing address record' clearly indicate modification of existing data in a reversible manner.
Attacks that exploit this kind of access
Update an existing address record. 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_address: 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_address 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_address 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_address. 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_address 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 →