Capture a screenshot of the current Blender 3D viewport.
AI agents call get_viewport_screenshot to retrieve information from Blender without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual information (a screenshot/image) from the viewport without creating, modifying, deleting, executing code, or causing financial impact. It is purely observational and has no side effects on the Blender scene or any external systems. The blast radius of misuse is minimal—an agent could at most capture unwanted screenshots of the viewport, which poses no security or operational risk.
From the tool's definition Tool name 'get_viewport_screenshot' and description 'Capture a screenshot of the current Blender 3D viewport' indicate read-only retrieval of visual data with no modifications to the scene or model state.
Documented attack patterns abuse exactly the kind of access get_viewport_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for get_viewport_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"get_viewport_screenshot": {}
}
} get_viewport_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Capture a screenshot of the current Blender 3D viewport. It is categorised as a Read tool in the Blender 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 Blender. 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 (vertiiii/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blender, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.