AI agents use add_project 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.
This tool creates a new project in OmniFocus, which is a reversible write operation. The user can delete or modify the project afterward. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The blast radius is medium because task/project misconfiguration could cause organizational confusion, but the action is not destructive or irreversible.
From the tool's definition Tool name is 'add_project' and description states 'Add a new project to OmniFocus'. The verb 'add' and 'new' clearly indicate creation of data.
Documented attack patterns abuse exactly the kind of access add_project 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 add_project:
{
"version": "1",
"default": "deny",
"tools": {
"add_project": {
"limits": [
{
"counter": "add_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_project 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.
Add a new project to OmniFocus. 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 add_project: 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.
add_project 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 add_project 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 add_project. 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.
add_project 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.