remove_local_extension
Remove a local workflow extension from the registry.
This record as markdown: /tools/todos/remove-local-extension.md
What remove_local_extension does on Todos
AI agents call remove_local_extension 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_local_extension is rated Critical
The tool removes an extension from the registry, which is an irreversible deletion operation. Once removed from the registry, the workflow extension configuration is gone and would need to be re-added. This qualifies as Destructive rather than Write since registry removal is not easily reversible.
From the tool's definition Remove a local workflow extension from the registry
Attacks that exploit this kind of access
The rule that runs remove_local_extension 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_local_extension, this is the rule to start with:
remove_local_extension 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_local_extension call is checked against it from then on.
Questions about remove_local_extension
Remove a local workflow extension from the registry. 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_local_extension: 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_local_extension 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_local_extension 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_local_extension. 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_local_extension 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