Get tasks from OmniFocus forecast perspective (due/deferred tasks in date range)
AI agents call get_forecast_tasks to retrieve information from OmniFocus MCP Enhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve task data based on date-based filtering criteria. It has no side effects, does not modify state, and poses minimal risk even if misused by an agent—the worst outcome would be retrieving an unintended subset of tasks. This clearly falls under the Read category.
From the tool's definition The tool 'get_forecast_tasks' retrieves tasks from OmniFocus forecast perspective with filtering by due/deferred dates.
Documented attack patterns abuse exactly the kind of access get_forecast_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus MCP Enhanced, and nothing reaches the server without passing your rules. This is the rule we recommend for get_forecast_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get_forecast_tasks": {}
}
}get_forecast_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get tasks from OmniFocus forecast perspective (due/deferred tasks in date range). It is categorised as a Read tool in the OmniFocus MCP Enhanced MCP Server, which means it retrieves data without modifying state.
Register the OmniFocus MCP Enhanced 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 OmniFocus MCP Enhanced. Nothing to install.
get_forecast_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_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.
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.
get_forecast_tasks is provided by the OmniFocus MCP Enhanced MCP server (jqlts1/omnifocus-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Enhanced, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 OmniFocus MCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.