search_messages
Searches iMessage conversations by content, sender name, or date range.
This record as markdown: /tools/com-local-mcp-local-mcp/search-messages.md
What search_messages does on Local
AI agents call search_messages to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max results (default 30) |
query | string | — | Text to search for in message content (optional if from_sender is set) |
since | string | — | ISO8601 date — only return messages on or after this date (optional, e.g. '2026-04-10' or '2026-04-10T00:00:00Z') |
until | string | — | ISO8601 date — only return messages on or before this date (optional). Combine with 'since' to search a date range with no text query. |
from_sender | string | — | Substring of sender name/handle to filter by (optional) |
Parameters from the server's own tool schema.
Why search_messages is rated Low
Even though search_messages only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_messages, this is the rule to start with:
search_messages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every search_messages call is checked against it from then on.
Questions about search_messages
Searches iMessage conversations by content, sender name, or date range. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
search_messages accepts 5 parameters: limit, query, since, until, from_sender. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for search_messages: 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 Local. Nothing to install.
search_messages 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 search_messages 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 search_messages. 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.
search_messages is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue