search_omnifocus_tasks
Searches OmniFocus tasks by name or note content.
This record as markdown: /tools/com-local-mcp-local-mcp/search-omnifocus-tasks.md
What search_omnifocus_tasks does on Local
AI agents call search_omnifocus_tasks 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_omnifocus_tasks is rated Low
This tool retrieves and filters task data from OmniFocus without creating, modifying, deleting, or executing any operations. It is purely informational. Severity is low because misuse would only expose task/note contents already stored locally on the user's Mac, with no side effects or destructive potential.
From the tool's definition Tool name includes 'search' and description states it 'Searches OmniFocus tasks by name or note content' — a query operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs search_omnifocus_tasks 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_omnifocus_tasks, this is the rule to start with:
search_omnifocus_tasks 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_omnifocus_tasks call is checked against it from then on.
Questions about search_omnifocus_tasks
Searches OmniFocus tasks by name or note content. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
search_omnifocus_tasks 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_omnifocus_tasks: 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_omnifocus_tasks 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_omnifocus_tasks 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_omnifocus_tasks. 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_omnifocus_tasks 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