delete-cache-v2
A destructive tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/delete-cache-v2.md
What delete-cache-v2 does on AdsPower LocalAPI MCP Server
AI agents call delete-cache-v2 to permanently remove resources in AdsPower LocalAPI MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-cache-v2 is rated Critical
Cache deletion is a destructive operation that cannot be easily undone. While cache can sometimes be regenerated, the tool's name clearly indicates permanent removal of stored data. Given the sibling tools (delete-browser, close-browser) on an AdsPower browser management server, this fits the destructive pattern of irreversible data removal.
From the tool's definition Tool name 'delete-cache-v2' explicitly indicates deletion/clearing of cached data. No description provided, but the 'delete-' prefix and '-v2' versioning strongly suggest an irreversible data removal operation.
Attacks that exploit this kind of access
The rule that runs delete-cache-v2 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdsPower LocalAPI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-cache-v2, this is the rule to start with:
delete-cache-v2 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 AdsPower LocalAPI MCP Server, apply this rule, and every delete-cache-v2 call is checked against it from then on.
Questions about delete-cache-v2
delete-cache-v2 is a destructive tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Destructive tool in the AdsPower LocalAPI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for delete-cache-v2: 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 AdsPower LocalAPI MCP Server. Nothing to install.
delete-cache-v2 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 delete-cache-v2 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 delete-cache-v2. 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.
delete-cache-v2 is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdsPower LocalAPI MCP Server, and thousands of servers like it.
Across the catalogue