This record as markdown: /tools/todos/remove-policy-pack.md
What remove_policy_pack does on Todos
AI agents call remove_policy_pack 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.
Why remove_policy_pack is rated Critical
Removing a policy pack is an irreversible destructive action that eliminates policy configurations. This falls under the Destructive category rather than Write because the operation cannot be easily undone and represents permanent loss of policy data.
From the tool's definition Tool name 'remove_policy_pack' uses the verb 'remove', which typically indicates deletion. Description states 'Remove a local policy pack', explicitly describing deletion of policy configuration data that cannot be reversed.
Attacks that exploit this kind of access
The rule that runs remove_policy_pack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_policy_pack, this is the rule to start with:
remove_policy_pack is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every remove_policy_pack call is checked against it from then on.
Questions about remove_policy_pack
Remove a local policy pack. 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_policy_pack: 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_policy_pack 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_policy_pack 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_policy_pack. 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_policy_pack 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.
More on Todos, and thousands of servers like it.
Across the catalogue