Call this tool to get a list of all tasks from OmniFocus, including completed ones. Use it when the user explicitly asks for
AI agents call get_all_tasks to retrieve information from OmniFocus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task data without side effects. It performs a read-only operation on OmniFocus data. The low severity reflects that exposing a task list, while potentially containing personal information, does not enable modification, deletion, or financial transactions—the blast radius is limited to information disclosure.
From the tool's definition Tool name 'get_all_tasks' and description 'get a list of all tasks from OmniFocus' indicate pure data retrieval with no modification, creation, or deletion capability.
Documented attack patterns abuse exactly the kind of access get_all_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_all_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get_all_tasks": {}
}
}get_all_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.
Call this tool to get a list of all tasks from OmniFocus, including completed ones. Use it when the user explicitly asks for. It is categorised as a Read tool in the OmniFocus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OmniFocus MCP Server MCP server in PolicyLayer and add a rule for get_all_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 Server. Nothing to install.
get_all_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_all_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_all_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_all_tasks is provided by the OmniFocus MCP Server MCP server (mdoel/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Server, 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.
4 OmniFocus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.