update-contact
Modify existing contact. Returns: updated contact with new etag. Use when: changing contact details. Note: requires updatePersonFields to specify what to update.
This record as markdown: /tools/199-biotechnologies-mcp-google/update-contact.md
What update-contact does on MCP Google Workspace
AI agents use update-contact to create or update resources in MCP Google Workspace, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Workspace environment.
Why update-contact is rated Medium
This tool creates or modifies contact data reversibly via the update operation. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or move money (Financial). The severity is medium because unauthorized modification of contacts could enable social engineering, impersonation, or communication interception, but the damage is limited to contact metadata and reversible.
From the tool's definition Tool description states 'Modify existing contact' and 'changing contact details', which indicates reversible modification of data. The return of 'updated contact with new etag' confirms the update operation completes successfully.
Attacks that exploit this kind of access
The rule that runs update-contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update-contact, this is the rule to start with:
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 MCP Google Workspace, apply this rule, and every update-contact call is checked against it from then on.
Questions about update-contact
Modify existing contact. Returns: updated contact with new etag. Use when: changing contact details. Note: requires updatePersonFields to specify what to update. It is categorised as a Write tool in the MCP Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Workspace 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 Workspace. 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 Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
This server
Across the catalogue