Remove a local planning capacity profile.
AI agents call remove_capacity_profile to permanently remove resources in Todos — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation ('remove') on a capacity profile, which cannot be undone. This is a destructive action that eliminates stored configuration state. While not as critical as removing all tasks, deleting planning capacity profiles could disrupt AI agent task scheduling and planning if profiles are accidentally or maliciously removed.
From the tool's definition Tool name contains 'remove' combined with description 'Remove a local planning capacity profile' - indicates irreversible deletion of configuration data.
Attacks that exploit this kind of access
Remove a local planning capacity profile. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos MCP server in PolicyLayer and add a rule for remove_capacity_profile: 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 Todos. Nothing to install.
remove_capacity_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_capacity_profile 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 remove_capacity_profile. 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.
remove_capacity_profile is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →