Low Risk

get_task_by_id

Get information about a specific task by ID or name

How to control get_task_by_id ↓

What get_task_by_id does on OmniFocus MCP Enhanced

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

Low Risk

Why get_task_by_id needs a policy

This tool retrieves task information by identifier without creating, modifying, or deleting any data. It is a straightforward read operation with no side effects or ability to alter the task management system state.

From the tool's definition Tool name 'get_task_by_id' and description 'Get information about a specific task by ID or name' indicate retrieval/query of existing data with no modification or deletion.

Documented attack patterns abuse exactly the kind of access get_task_by_id gives an agent:

How to control get_task_by_id

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_task_by_id:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_task_by_id": {}
  }
}

get_task_by_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OmniFocus MCP Enhanced — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_task_by_id

What does the get_task_by_id tool do? +

Get information about a specific task by ID or name. It is categorised as a Read tool in the OmniFocus MCP Enhanced MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task_by_id? +

Register the OmniFocus MCP Enhanced 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 OmniFocus MCP Enhanced. Nothing to install.

What risk level is get_task_by_id? +

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

Can I rate-limit get_task_by_id? +

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.

How do I block get_task_by_id completely? +

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.

What MCP server provides get_task_by_id? +

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

Enforce policy on every OmniFocus MCP Enhanced tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.