Creates or updates the TODO.md file in .project/ directory. Use this when adding tasks, marking items complete, or updating task status. Intelligently organizes tasks into sections (In Progress, Next Up, Blocked, Completed).
AI agents use create_or_update_todo to create or update resources in Project MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project MCP environment.
This tool modifies project state by creating or updating task records, which is a Write operation (reversible data modification). Severity is medium because while task management affects project coordination, the impact is limited to internal documentation without financial consequences, external system effects, or data destruction.
From the tool's definition Tool description explicitly states 'Creates or updates the TODO.md file' and 'adding tasks, marking items complete, or updating task status' — all reversible modifications to project documentation.
Documented attack patterns abuse exactly the kind of access create_or_update_todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_or_update_todo:
{
"version": "1",
"default": "deny",
"tools": {
"create_or_update_todo": {
"limits": [
{
"counter": "create_or_update_todo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_or_update_todo 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.
Creates or updates the TODO.md file in .project/ directory. Use this when adding tasks, marking items complete, or updating task status. Intelligently organizes tasks into sections (In Progress, Next Up, Blocked, Completed). It is categorised as a Write tool in the Project MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project MCP server in PolicyLayer and add a rule for create_or_update_todo: 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 Project MCP. Nothing to install.
create_or_update_todo 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_or_update_todo 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_or_update_todo. 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_or_update_todo is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project MCP, 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.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.