Check Apple Contacts access and return aggregate counts without exposing contact values.
AI agents call contacts_status to retrieve information from Apple Contacts MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information and aggregate statistics from Apple Contacts with explicit design to avoid exposing actual contact data. It has no side effects, does not modify, delete, or execute operations—it purely queries and reports summary information. This is a classic Read operation with minimal risk.
From the tool's definition Tool description states it 'Check[s] Apple Contacts access and return[s] aggregate counts without exposing contact values.' The word 'without exposing contact values' and 'aggregate counts' indicate this performs queries only, returning metadata rather than…
Attacks that exploit this kind of access
Check Apple Contacts access and return aggregate counts without exposing contact values. It is categorised as a Read tool in the Apple Contacts MCP MCP Server, which means it retrieves data without modifying state.
Register the Apple Contacts MCP server in PolicyLayer and add a rule for contacts_status: 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 Apple Contacts MCP. Nothing to install.
contacts_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the contacts_status 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 contacts_status. 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.
contacts_status is provided by the Apple Contacts MCP server (lu-wo/apple-contacts-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 →