AI agents call get_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 task data from OmniFocus. It has no side effects—it queries and returns existing data without creating, modifying, deleting, or executing operations. The 'get_' prefix strongly indicates a Read operation. Confidence is high despite the empty description because the naming pattern is unambiguous and consistent with other Read operations on the server.
From the tool's definition Tool name 'get_tasks' indicates a retrieval operation. The description is empty, but the naming convention (get_*) is consistent with the sibling tool 'get_focus' and 'get_folders' on the same server, which are clearly Read operations.
Documented attack patterns abuse exactly the kind of access get_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_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get_tasks": {}
}
}get_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. 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_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_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_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_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_tasks is provided by the OmniFocus MCP Server MCP server (s-morgan-jeffries/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.
21 OmniFocus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.