AI agents use add_todo to create or update resources in Software Planning Tool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Software Planning Tool environment.
The tool creates reversible data (a todo item) with no side effects beyond adding a record. It does not execute external code, delete data, or trigger financial transactions. This is a standard Write operation that can be easily modified or removed later.
From the tool's definition Tool description states 'Add a new todo item to the current plan' — this creates a new data item in the planning system.
Documented attack patterns abuse exactly the kind of access add_todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Software Planning Tool, and nothing reaches the server without passing your rules. This is the rule we recommend for add_todo:
{
"version": "1",
"default": "deny",
"tools": {
"add_todo": {
"limits": [
{
"counter": "add_todo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
Add a new todo item to the current plan. It is categorised as a Write tool in the Software Planning Tool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Software Planning Tool MCP server in PolicyLayer and add a rule for add_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 Software Planning Tool. Nothing to install.
add_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 add_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 add_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.
add_todo is provided by the Software Planning Tool MCP server (nighttrek/software-planning-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Software Planning Tool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Software Planning Tool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.