list_omnifocus_tasks
Lists tasks from OmniFocus. Filter by project, tag, inbox, due today, or flagged status.
This record as markdown: /tools/com-local-mcp-local-mcp/list-omnifocus-tasks.md
What list_omnifocus_tasks does on Local
AI agents call list_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 |
|---|---|---|---|
tag | string | — | |
inbox | boolean | — | |
limit | integer | — | |
flagged | boolean | — | |
project | string | — | |
due_today | boolean | — | |
include_completed | boolean | — |
Parameters from the server's own tool schema.
Why list_omnifocus_tasks is rated Low
The tool performs task querying and listing with optional filtering—a retrieval operation with no side effects or state modification. It poses minimal risk if accessed by an AI agent since it only exposes existing task information that is typically within the user's own system.
From the tool's definition Tool name 'list_omnifocus_tasks' and description 'Lists tasks from OmniFocus' indicate a read-only operation that retrieves task data without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
The rule that runs list_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 list_omnifocus_tasks, this is the rule to start with:
list_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 list_omnifocus_tasks call is checked against it from then on.
Questions about list_omnifocus_tasks
Lists tasks from OmniFocus. Filter by project, tag, inbox, due today, or flagged status. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
list_omnifocus_tasks accepts 7 parameters: tag, inbox, limit, flagged, project, due_today, include_completed. 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 list_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.
list_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 list_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 list_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.
list_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