Update the completion status of a todo item
AI agents use update_todo_status 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.
This tool modifies data (todo item status) but does not create/delete records or trigger external operations. The change is fully reversible and has minimal blast radius. It fits the Write category: creates or modifies data reversibly. Severity is low because misconfiguring a todo status has no downstream impact on finances, system integrity, or data loss.
From the tool's definition Tool name 'update_todo_status' and description 'Update the completion status of a todo item' indicates modification of existing data. The action is reversible—status can be changed back—and affects only a single todo item's state field.
Documented attack patterns abuse exactly the kind of access update_todo_status 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 update_todo_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_todo_status": {
"limits": [
{
"counter": "update_todo_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_todo_status 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.
Update the completion status of a todo item. 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 update_todo_status: 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.
update_todo_status 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 update_todo_status 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 update_todo_status. 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.
update_todo_status 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.