Advanced task filtering for ONE project. For filtering across 2+ projects, use batch_filter_tasks instead (single API call). Supports status, dates, tags, search, and more.
AI agents call filter_tasks to retrieve information from OmniFocus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing tasks based on specified criteria (status, dates, tags, search). It has no capacity to create, modify, delete, or execute external operations. The blast radius of misuse is minimal—a user could retrieve unintended task information, but no data is changed or deleted. Classified as Read with low severity.
From the tool's definition Tool performs filtering/querying operations with no side effects: 'Advanced task filtering', 'Supports status, dates, tags, search'. The description emphasizes retrieving and organizing data without modification.
Attacks that exploit this kind of access
Advanced task filtering for ONE project. For filtering across 2+ projects, use batch_filter_tasks instead (single API call). Supports status, dates, tags, search, and more. It is categorised as a Read tool in the OmniFocus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OmniFocus MCP Server 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 OmniFocus MCP Server. 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 OmniFocus MCP Server MCP server (mojenmojen/of-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 →