// SCAN REPORT

Apple Contacts MCP

7 tools. 5 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

5 can modify or destroy data

2 read-only

7 tools total

Community server · catalogue entry verified 29/06/2026

How to control Apple Contacts MCP ↓

TOOL MAP

What Apple Contacts MCP exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Apple Contacts MCP tools

Destructive · High delete_contact Deletion of contact records is irreversible and represents data loss. Destructive · High test_roundtrip Even though the contact created is a dummy/test contact, the tool performs a deletion as a final step, which is irreversible. Write · Medium append_contact_note This tool modifies existing contact data by appending text to a note field. Write · Medium create_contact This tool creates new contact records, which is a Write operation (data creation).

5 of Apple Contacts MCP's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Apple Contacts MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Contacts MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_contact": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "append_contact_note": {
    "limits": [
      {
        "counter": "append_contact_note_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "contacts_status": {
    "limits": [
      {
        "counter": "contacts_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Apple Contacts MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON APPLE CONTACTS →

Instant setup, no code required.

FULL CATALOGUE

All 7 Apple Contacts MCP tools

DESTRUCTIVE 2 tools

Destructive delete_contact Delete an Apple Contact by contactId. Dry-run by default and requires confirmPhrase= Destructive test_roundtrip Create, edit, verify, and delete one dummy contact. Requires confirm=true.

WRITE 3 tools

Write append_contact_note Append a dated interaction log entry to a contact note. Dry-run by default; actual writes require dryRun=false Write create_contact Create an Apple Contact. Dry-run by default; actual writes require dryRun=false and confirm=true. Write update_contact Update an Apple Contact by contactId. Dry-run by default; actual writes require dryRun=false and confirm=true.

READ 2 tools

Read contacts_status Check Apple Contacts access and return aggregate counts without exposing contact values. Read search_contacts Search Apple Contacts by name, organization, job title, email, or phone.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Apple Contacts MCP

Can an AI agent delete data through the Apple Contacts MCP server? +

Yes. The Apple Contacts MCP server exposes 2 destructive tools including delete_contact, test_roundtrip. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Apple Contacts MCP? +

The Apple Contacts MCP server has 3 write tools including append_contact_note, create_contact, update_contact. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Apple Contacts MCP.

How many tools does the Apple Contacts MCP server expose? +

7 tools across 4 categories: Destructive, Execute, Read, Write. 2 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Apple Contacts MCP? +

Register the Apple Contacts MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Apple Contacts MCP tool call.

Deterministic rules across all 7 Apple Contacts MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON APPLE CONTACTS →

Instant setup, no code required.

7 Apple Contacts MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.