PREFERRED: Filter tasks across multiple projects in ONE call. Always use this instead of multiple filter_tasks calls when querying 2+ projects.
AI agents call batch_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 performs filtering and querying of tasks across projects without creating, modifying, deleting, or executing external operations. It is a retrieval operation with no side effects, clearly fitting the Read category. Low severity because misuse would only expose task data visibility rather than causing destructive or financial harm.
From the tool's definition Tool description states 'Filter tasks across multiple projects' and 'querying' — these are read-only query operations with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
PREFERRED: Filter tasks across multiple projects in ONE call. Always use this instead of multiple filter_tasks calls when querying 2+ projects. 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 batch_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.
batch_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 batch_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 batch_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.
batch_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 →