# view_image

Display an image in the system

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

## Facts

- Tool: `view_image`
- Server: Replicate MCP Server (`deepfates/mcp-replicate`) — https://policylayer.com/tools/deepfates-mcp-replicate.md
- Homepage: https://github.com/deepfates/mcp-replicate
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "view_image",
    "arguments": {}
  }
}
```

## Why view_image is rated Low

This tool retrieves and displays image data without creating, modifying, deleting, or executing operations. It is a read-only operation that presents existing content to the user. The severity is low because image viewing has minimal blast radius—no data is altered, deleted, or at risk of financial impact.

From the tool's own definition: "Tool name 'view_image' and description 'Display an image in the system' indicate retrieval and display of image data with no modification or side effects."

## Use case

AI agents call view_image to retrieve information from Replicate MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "view_image": {}
  }
}
```

## Other tools on Replicate MCP Server (12)

- `clear_image_cache` — Destructive — https://policylayer.com/tools/deepfates-mcp-replicate/clear-image-cache.md
- `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

## 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