Medium Risk

update_contact

Update an existing contact

How to control update_contact ↓

What update_contact does on Mcp Ap2

AI agents use update_contact to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.

Medium Risk

Why update_contact needs a policy

This tool creates or modifies data in a reversible manner (typical contact record updates can be undone or re-edited). While it operates within a financial/payment protocol context (AP2), the action itself is not financial (no money moves), not destructive (changes are reversible), and not executing arbitrary code. It is a Write operation.

From the tool's definition The tool is named 'update_contact' and described as 'Update an existing contact', which modifies existing data reversibly.

Documented attack patterns abuse exactly the kind of access update_contact gives an agent:

How to control update_contact

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for update_contact:

policy.json
{
  "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.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_contact

What does the update_contact tool do? +

Update an existing contact. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_contact? +

Register the Mcp Ap2 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 Ap2. Nothing to install.

What risk level is update_contact? +

update_contact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_contact? +

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.

How do I block update_contact completely? +

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.

What MCP server provides update_contact? +

update_contact is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.