Update a specific field of an existing contact
AI agents use update_contact to create or update resources in macOS MCP Servers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your macOS MCP Servers environment.
This tool creates or modifies contact records reversibly. While it could potentially be misused to alter contact information (email addresses, phone numbers, relationships), the changes are not destructive—they can be undone or corrected.
From the tool's definition Tool name 'update_contact' and description 'Update a specific field of an existing contact' indicate modification of existing contact data. The verb 'update' is explicitly used, which is characteristic of Write operations that reversibly modify data.
Attacks that exploit this kind of access
Update a specific field of an existing contact. It is categorised as a Write tool in the macOS MCP Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the macOS MCP Servers 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 macOS MCP Servers. 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 macOS MCP Servers MCP server (tdisawas0github/mcp). 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 →