Get information about a specific task by ID or name, including attachment metadata when available.
AI agents call get_task_by_id 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 existing task data without side effects. It queries the OmniFocus database to fetch information about a task and its associated metadata. No data is created, modified, deleted, or executed. This is a straightforward read operation with minimal risk—worst case, an agent could expose task details an AI shouldn't see, but cannot cause destructive or financial harm.
From the tool's definition Tool name 'get_task_by_id' and description explicitly states 'Get information about a specific task' with no mention of modification, deletion, or execution. Returns data retrieval only: 'task by ID or name, including attachment metadata'.
Attacks that exploit this kind of access
Get information about a specific task by ID or name, including attachment metadata when available. 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_task_by_id: 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_task_by_id 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_task_by_id 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_task_by_id. 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_task_by_id 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 →