remove_tool
Remove a tool from your personal collection.
This record as markdown: /tools/namastexlabs-automagik-tools/remove-tool.md
What remove_tool does on Automagik Tools
AI agents call remove_tool to permanently remove resources in Automagik Tools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_tool is rated Critical
This tool performs an irreversible deletion action on stored tool definitions. Once removed from the collection, the tool configuration is lost and cannot be recovered through normal operation. While not a data deletion in the traditional sense, removing tools from a configured collection constitutes destructive modification of system state. An agent misusing this could delete critical tools needed for operations.
From the tool's definition Tool name is 'remove_tool' and description states 'Remove a tool from your personal collection.' The verb 'remove' combined with deletion from a personal collection indicates irreversible removal of configuration or tool definitions.
Attacks that exploit this kind of access
The rule that runs remove_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_tool, this is the rule to start with:
remove_tool 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 Automagik Tools, apply this rule, and every remove_tool call is checked against it from then on.
Questions about remove_tool
Remove a tool from your personal collection. It is categorised as a Destructive tool in the Automagik Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for remove_tool: 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 Automagik Tools. Nothing to install.
remove_tool 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_tool 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_tool. 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_tool is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
Across the catalogue