# get_viewport_screenshot

Capture a screenshot of the current viewport

Agent View of the PolicyLayer registry record for `get_viewport_screenshot`. HTML page: https://policylayer.com/tools/aryeon0228-blendermcp/get-viewport-screenshot

## Facts

- Tool: `get_viewport_screenshot`
- Server: BlenderMCP (`aryeon0228/blendermcp`) — https://policylayer.com/tools/aryeon0228-blendermcp.md
- Homepage: https://github.com/Aryeon0228/BlenderMCP
- 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": "get_viewport_screenshot",
    "arguments": {}
  }
}
```

## Why get_viewport_screenshot is rated Low

The tool retrieves a visual representation of the current state of the Blender viewport. It performs no side effects, creates no new objects, executes no code, and does not modify the scene or persists any data. This is purely a read operation analogous to a query or fetch. Even in a misuse scenario, the worst outcome would be information disclosure of what is currently on screen, making it low severity.

From the tool's own definition: "Tool name is 'get_viewport_screenshot' and description states 'Capture a screenshot of the current viewport' — this is a retrieval operation that captures visual data without modifying, deleting, or executing operations in Blender."

## Use case

AI agents call get_viewport_screenshot to retrieve information from BlenderMCP 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 BlenderMCP:

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

## Other tools on BlenderMCP (11)

- `delete_object` — Destructive — https://policylayer.com/tools/aryeon0228-blendermcp/delete-object.md
- `execute_blender_code` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/execute-blender-code.md
- `render_scene` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/render-scene.md
- `scale_object` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/scale-object.md
- `get_object_info` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-object-info.md
- `get_scene_info` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-scene-info.md
- `create_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/create-object.md
- `move_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/move-object.md
- `rotate_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/rotate-object.md
- `save_blend_file` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/save-blend-file.md
- `set_material` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/set-material.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=aryeon0228-blendermcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aryeon0228-blendermcp