# clear_image_cache

Clear the image viewer cache

Agent View of the PolicyLayer registry record for `clear_image_cache`. HTML page: https://policylayer.com/tools/deepfates-mcp-replicate/clear-image-cache

## Facts

- Tool: `clear_image_cache`
- Server: Replicate MCP Server (`deepfates/mcp-replicate`) — https://policylayer.com/tools/deepfates-mcp-replicate.md
- Homepage: https://github.com/deepfates/mcp-replicate
- 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": "clear_image_cache",
    "arguments": {}
  }
}
```

## Why clear_image_cache is rated Critical

The tool performs cache clearing, which permanently removes stored image data. While not system-critical, clearing image caches cannot be undone and constitutes irreversible data removal (purging). This is more severe than reversible Write operations but lower than critical data destruction, as the impact is localized to cache rather than primary data storage.

From the tool's own definition: "clear_image_cache - 'Clear the image viewer cache' indicates irreversible deletion of cached image data"

## Use case

AI agents call clear_image_cache to permanently remove resources in Replicate 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 Replicate MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_image_cache"
  ]
}
```

## Other tools on Replicate MCP Server (12)

- `cancel_prediction` — Execute — https://policylayer.com/tools/deepfates-mcp-replicate/cancel-prediction.md
- `create_and_poll_prediction` — Execute — https://policylayer.com/tools/deepfates-mcp-replicate/create-and-poll-prediction.md
- `create_prediction` — Execute — https://policylayer.com/tools/deepfates-mcp-replicate/create-prediction.md
- `get_collection` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/get-collection.md
- `get_image_cache_stats` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/get-image-cache-stats.md
- `get_model` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/get-model.md
- `get_prediction` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/get-prediction.md
- `list_collections` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/list-collections.md
- `list_models` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/list-models.md
- `list_predictions` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/list-predictions.md
- `search_models` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/search-models.md
- `view_image` — Read — https://policylayer.com/tools/deepfates-mcp-replicate/view-image.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=deepfates-mcp-replicate · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepfates-mcp-replicate