get_forecast_tasks

Get tasks from OmniFocus forecast perspective (due/deferred tasks in date range)

Server Codex Omnifocus phd-peter/codex-omnifocus-mcp
Category Read
Risk class Low
Parameters 00 required

What get_forecast_tasks does on Codex Omnifocus

AI agents call get_forecast_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.

Why get_forecast_tasks needs a policy

This tool queries OmniFocus to fetch tasks based on status and date criteria. It performs no creation, modification, deletion, or execution of external operations. The operation is a simple retrieval of existing task data, making it a standard Read operation with low risk. Severity is low since misuse would only result in unwanted task visibility, not data loss or system compromise.

From the tool's definition get_forecast_tasks retrieves tasks from a forecast perspective within a date range (described as 'due/deferred tasks in date range'). The verb 'Get' and the read-only nature of querying forecast data indicate retrieval without modification.

Questions about get_forecast_tasks

What does the get_forecast_tasks tool do? +

Get tasks from OmniFocus forecast perspective (due/deferred tasks in date range). It is categorised as a Read tool in the Codex Omnifocus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_forecast_tasks? +

Register the Codex Omnifocus MCP server in PolicyLayer and add a rule for get_forecast_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.

What risk level is get_forecast_tasks? +

get_forecast_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_forecast_tasks? +

Yes. Add a rate_limit block to the get_forecast_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.

How do I block get_forecast_tasks completely? +

Set action: deny in the PolicyLayer policy for get_forecast_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.

What MCP server provides get_forecast_tasks? +

get_forecast_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.