List all contacts from the macOS Contacts app with their phone numbers
AI agents call list-contacts to retrieve information from iMessage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information from the macOS Contacts app without modifying, deleting, or executing any operations. It is a simple enumeration/list operation that falls squarely within the Read category. The severity is low because contact lists, while potentially sensitive personal information, are static data that cannot cause damage through reading alone.
From the tool's definition Tool name 'list-contacts' and description 'List all contacts from the macOS Contacts app with their phone numbers' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list-contacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and iMessage MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-contacts:
{
"version": "1",
"default": "deny",
"tools": {
"list-contacts": {}
}
}list-contacts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all contacts from the macOS Contacts app with their phone numbers. It is categorised as a Read tool in the iMessage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the iMessage MCP Server MCP server in PolicyLayer and add a rule for list-contacts: 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 iMessage MCP Server. Nothing to install.
list-contacts 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 list-contacts 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 list-contacts. 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.
list-contacts is provided by the iMessage MCP Server MCP server (sameelarif/imessage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from iMessage MCP Server, 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.
14 iMessage MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.