Capture a screenshot of the current Blender 3D viewport.
AI agents call get_viewport_screenshot to retrieve information from BlenderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries visual data from Blender's viewport (a screenshot) with no side effects, state changes, or external operations. It is a straightforward Read operation. Severity is low because viewport screenshots pose minimal security risk—they contain only current visual state of a 3D scene that the user is already viewing.
From the tool's definition Tool name 'get_viewport_screenshot' and description 'Capture a screenshot of the current Blender 3D viewport' indicate a read-only operation that retrieves visual data without modifying state or triggering external operations.
Attacks that exploit this kind of access
Capture a screenshot of the current Blender 3D viewport. It is categorised as a Read tool in the BlenderMCP MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for get_viewport_screenshot: 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 BlenderMCP. Nothing to install.
get_viewport_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_viewport_screenshot 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 get_viewport_screenshot. 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.
get_viewport_screenshot is provided by the Blender MCP server (wenyen-hsu/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →