This record as markdown: /tools/com-local-mcp-local-mcp/search-notes.md
What search_notes does on Local
AI agents call search_notes 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 | — | |
query | string | Yes |
Parameters from the server's own tool schema.
Why search_notes is rated Low
This tool retrieves or queries data from Apple Notes without creating, modifying, executing operations, or deleting anything. It is a straightforward read operation. Severity is low because searching local notes carries minimal risk even if misused by an AI agent—at worst it leaks information the agent shouldn't access, but causes no destructive or external damage.
From the tool's definition The tool 'search_notes' is explicitly described as 'Searches Apple Notes by title or content.' The verb 'searches' and the parameters (title, content) indicate a read-only query operation with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_notes 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_notes, this is the rule to start with:
search_notes 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_notes call is checked against it from then on.
Questions about search_notes
Searches Apple Notes by title or content. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
search_notes accepts 2 parameters: limit, query. Required: query. 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_notes: 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_notes 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_notes 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_notes. 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_notes 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