Create a new tag in OmniFocus, optionally nested under an existing parent tag
AI agents use create_tag to create or update resources in OmniFocus-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniFocus-MCP environment.
Creating a tag is a write operation that adds new metadata to the OmniFocus system. It is reversible (tags can be deleted), affects only the tag hierarchy, and has minimal blast radius if misused by an AI agent. It does not delete data (Destructive), execute external code (Execute), move money (Financial), or modify existing tasks/projects in ways that cascade broadly.
From the tool's definition Tool description explicitly states 'Create a new tag in OmniFocus', which is a reversible data creation operation. Tags are metadata entities that can be deleted or modified without affecting core task data.
Documented attack patterns abuse exactly the kind of access create_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_tag:
{
"version": "1",
"default": "deny",
"tools": {
"create_tag": {
"limits": [
{
"counter": "create_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_tag stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new tag in OmniFocus, optionally nested under an existing parent tag. It is categorised as a Write tool in the OmniFocus-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OmniFocus- MCP server in PolicyLayer and add a rule for create_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 OmniFocus-MCP. Nothing to install.
create_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_tag is provided by the OmniFocus- MCP server (themotionmachine/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 OmniFocus-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 OmniFocus-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.