Search for a contact by name and get their phone number. Use this FIRST when the user mentions someone by name instead of phone number. Searches both iMessage history and macOS Contacts.
AI agents call find-contact 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 performs a read-only query operation to retrieve contact information (phone number) from iMessage history and macOS Contacts. It has no side effects—it neither modifies, deletes, executes code, nor triggers financial transactions.
From the tool's definition Tool description states it 'Search[es] for a contact by name and get their phone number' and 'Searches both iMessage history and macOS Contacts.' The verb is search/get, which retrieves data without modification.
Documented attack patterns abuse exactly the kind of access find-contact 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 find-contact:
{
"version": "1",
"default": "deny",
"tools": {
"find-contact": {}
}
}find-contact 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.
Search for a contact by name and get their phone number. Use this FIRST when the user mentions someone by name instead of phone number. Searches both iMessage history and macOS Contacts. 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 find-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 iMessage MCP Server. Nothing to install.
find-contact 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 find-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 find-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.
find-contact 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.