Get flagged tasks from OmniFocus with optional project filtering
AI agents call get_flagged_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.
This tool retrieves and filters existing flagged tasks without creating, modifying, deleting, or executing operations. It has no side effects and poses minimal risk—the primary concern would be unauthorized access to task data, but the tool itself cannot harm the system or user's data.
From the tool's definition Tool name 'get_flagged_tasks' and description 'Get flagged tasks from OmniFocus with optional project filtering' indicate a retrieval operation. The verb 'Get' and lack of any modification language confirm this is a query-only action.
Attacks that exploit this kind of access
Get flagged tasks from OmniFocus with optional project filtering. 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 get_flagged_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.
get_flagged_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 get_flagged_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 get_flagged_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.
get_flagged_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 →