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 the current state of the Blender viewport by capturing its visual representation. It produces no side effects, does not modify scene data, does not execute code, and does not delete or create assets. It is purely informational, similar to a 'get' or 'fetch' operation. Misuse by an AI agent would result in minimal harm—at worst, exposing the current viewport contents.
From the tool's definition Tool name 'get_viewport_screenshot' and description 'Capture a screenshot of the current Blender 3D viewport' indicate a retrieval operation that captures visual data without modifying state or triggering external operations.
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 BlenderMCP, 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 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 (nanashi1526/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BlenderMCP, 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 BlenderMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.