Get tasks filtered by OmniFocus tags. Use this for tag names, not custom perspective names.
AI agents call get_tasks_by_tag 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 queries and retrieves tasks from a local OmniFocus database based on tag filters. It performs a read-only operation with no capability to create, modify, delete, or execute external actions. The blast radius of misuse is minimal—an AI agent could retrieve sensitive task information but cannot alter state or cause harm beyond information disclosure.
From the tool's definition Tool name 'get_tasks_by_tag' and description 'Get tasks filtered by OmniFocus tags' indicate retrieval/querying of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get tasks filtered by OmniFocus tags. Use this for tag names, not custom perspective names. 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_tasks_by_tag: 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_tasks_by_tag 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_tasks_by_tag 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_tasks_by_tag. 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_tasks_by_tag 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 →