Advanced task filtering with unlimited perspective combinations - status, dates, projects, tags, search, and more
AI agents call filter_tasks to retrieve information from Codex Omnifocus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is designed to search and retrieve tasks from the OmniFocus database using multiple filter criteria. Filtering is a read-only operation that returns results without creating, modifying, deleting, or executing any actions. The sibling tools clearly show that modification operations (add_omnifocus_task, edit_item, batch_remove_items) are separate, confirming that filter_tasks is purely read-based.
From the tool's definition Tool performs 'Advanced task filtering' which is a query operation that retrieves and filters existing tasks based on various criteria (status, dates, projects, tags, search).
Attacks that exploit this kind of access
Advanced task filtering with unlimited perspective combinations - status, dates, projects, tags, search, and more. It is categorised as a Read tool in the Codex Omnifocus MCP Server, which means it retrieves data without modifying state.
Register the Codex Omnifocus MCP server in PolicyLayer and add a rule for filter_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 Codex Omnifocus. Nothing to install.
filter_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 filter_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 filter_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.
filter_tasks is provided by the Codex Omnifocus MCP server (phd-peter/codex-omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →