AI agents use update_contact to create or update resources in MCP Google Contacts Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Contacts Server environment.
The tool modifies existing contact data in Google Contacts. This is a Write operation because updates are reversible (prior data can be restored). Severity is medium because misuse could alter contact information affecting communication (e.g., changing email addresses or phone numbers), but the changes can be undone.
From the tool's definition Tool description states 'Update an existing contact,' and server description confirms it enables 'updating...contacts within your Google account.' Update operations are reversible modifications of data.
Documented attack patterns abuse exactly the kind of access update_contact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Google Contacts Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_contact:
{
"version": "1",
"default": "deny",
"tools": {
"update_contact": {
"limits": [
{
"counter": "update_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Update an existing contact. It is categorised as a Write tool in the MCP Google Contacts Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Contacts 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 MCP Google Contacts 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 MCP Google Contacts Server MCP server (rayanzaki/mcp-google-contacts-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 MCP Google Contacts Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 MCP Google Contacts Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.