This record as markdown: /tools/io-github-ruvnet-claude-flow/todo-add.md
What todo_add does on Claude Flow
AI agents use todo_add to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why todo_add is rated Medium
This tool creates a new todo item, which is a Write operation. The action is reversible (the item can be deleted later), involves no code execution or external operations, and has minimal blast radius if misused—at worst, spurious tasks clutter a list. Severity is low because the impact is confined to task management with no financial, destructive, or system-level consequences.
From the tool's definition Tool name 'todo_add' and description 'Add a task to the todo list' indicate creation of new data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs todo_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For todo_add, this is the rule to start with:
todo_add 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every todo_add call is checked against it from then on.
Questions about todo_add
Add a task to the todo list. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for todo_add: 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 Claude Flow. Nothing to install.
todo_add 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 todo_add 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 todo_add. 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.
todo_add is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue