list_tasks_by_tag
AI agents call list_tasks_by_tag to retrieve information from MCP OmniFocus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries tasks filtered by a tag parameter. It does not create, modify, delete, or execute operations—it only returns data. The 'list_' prefix across the server's tool suite denotes read-only listing operations. Confidence is high despite missing description because the naming pattern is unambiguous.
From the tool's definition Tool name 'list_tasks_by_tag' follows the read-only 'list_*' pattern consistent with sibling tools like list_tasks, list_projects, list_tags, and list_inbox.
Attacks that exploit this kind of access
list_tasks_by_tag. It is categorised as a Read tool in the MCP OmniFocus MCP Server, which means it retrieves data without modifying state.
Register the MCP OmniFocus MCP server in PolicyLayer and add a rule for list_tasks_by_tag: 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 MCP OmniFocus. Nothing to install.
list_tasks_by_tag 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 list_tasks_by_tag 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 list_tasks_by_tag. 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.
list_tasks_by_tag is provided by the MCP OmniFocus MCP server (someposer/mcp-omnifocus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →