vacuum_reset_consumable
A destructive tool on the Tolpo MCP server.
This record as markdown: /tools/tolpo/vacuum-reset-consumable.md
What vacuum_reset_consumable does on Tolpo
AI agents call vacuum_reset_consumable to permanently remove resources in Tolpo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why vacuum_reset_consumable is rated Critical
An AI agent that decides to call vacuum_reset_consumable doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Tolpo is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs vacuum_reset_consumable safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tolpo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vacuum_reset_consumable, this is the rule to start with:
vacuum_reset_consumable 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 Tolpo, apply this rule, and every vacuum_reset_consumable call is checked against it from then on.
Questions about vacuum_reset_consumable
vacuum_reset_consumable is a destructive tool on the Tolpo MCP server. It is categorised as a Destructive tool in the Tolpo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tolpo MCP server in PolicyLayer and add a rule for vacuum_reset_consumable: 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 Tolpo. Nothing to install.
vacuum_reset_consumable 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 vacuum_reset_consumable 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 vacuum_reset_consumable. 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.
vacuum_reset_consumable is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tolpo, and thousands of servers like it.
Across the catalogue