# delete-cache-v2

A destructive tool on the AdsPower LocalAPI MCP Server MCP server.

Agent View of the PolicyLayer registry record for `delete-cache-v2`. HTML page: https://policylayer.com/tools/adspower-adspower-browser/delete-cache-v2

## Facts

- Tool: `delete-cache-v2`
- Server: AdsPower LocalAPI MCP Server (`adspower/adspower-browser`) — https://policylayer.com/tools/adspower-adspower-browser.md
- Homepage: https://github.com/AdsPower/adspower-browser
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete-cache-v2",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches AdsPower LocalAPI MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-cache-v2"
  ]
}
```

## Other tools on AdsPower LocalAPI MCP Server (46)

- `delete-browser` — Destructive — https://policylayer.com/tools/adspower-adspower-browser/delete-browser.md
- `delete-proxy` — Destructive — https://policylayer.com/tools/adspower-adspower-browser/delete-proxy.md
- `delete-tag` — Destructive — https://policylayer.com/tools/adspower-adspower-browser/delete-tag.md
- `click-element` — Execute — https://policylayer.com/tools/adspower-adspower-browser/click-element.md
- `close-all-profiles` — Execute — https://policylayer.com/tools/adspower-adspower-browser/close-all-profiles.md
- `close-browser` — Execute — https://policylayer.com/tools/adspower-adspower-browser/close-browser.md
- `connect-browser-with-ws` — Execute — https://policylayer.com/tools/adspower-adspower-browser/connect-browser-with-ws.md
- `download-kernel` — Execute — https://policylayer.com/tools/adspower-adspower-browser/download-kernel.md
- `drag-element` — Execute — https://policylayer.com/tools/adspower-adspower-browser/drag-element.md
- `evaluate-script` — Execute — https://policylayer.com/tools/adspower-adspower-browser/evaluate-script.md
- `fill-input` — Execute — https://policylayer.com/tools/adspower-adspower-browser/fill-input.md
- `hover-element` — Execute — https://policylayer.com/tools/adspower-adspower-browser/hover-element.md
- `iframe-click-element` — Execute — https://policylayer.com/tools/adspower-adspower-browser/iframe-click-element.md
- `navigate` — Execute — https://policylayer.com/tools/adspower-adspower-browser/navigate.md
- `open-browser` — Execute — https://policylayer.com/tools/adspower-adspower-browser/open-browser.md
- `open-new-page` — Execute — https://policylayer.com/tools/adspower-adspower-browser/open-new-page.md
- `press-key` — Execute — https://policylayer.com/tools/adspower-adspower-browser/press-key.md
- `scroll-element` — Execute — https://policylayer.com/tools/adspower-adspower-browser/scroll-element.md
- `select-option` — Execute — https://policylayer.com/tools/adspower-adspower-browser/select-option.md
- `new-fingerprint` — Other — https://policylayer.com/tools/adspower-adspower-browser/new-fingerprint.md
- `check-status` — Read — https://policylayer.com/tools/adspower-adspower-browser/check-status.md
- `get-application-list` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-application-list.md
- `get-browser-active` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-browser-active.md
- `get-browser-list` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-browser-list.md
- `get-cloud-active` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-cloud-active.md
- `get-group-list` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-group-list.md
- `get-kernel-list` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-kernel-list.md
- `get-opened-browser` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-opened-browser.md
- `get-page-html` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-page-html.md
- `get-page-visible-text` — Read — https://policylayer.com/tools/adspower-adspower-browser/get-page-visible-text.md
- …and 16 more: https://policylayer.com/tools/adspower-adspower-browser.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adspower-adspower-browser · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adspower-adspower-browser