Capture several camera angles in ONE call and return them all as images, so you can see the whole model and catch problems (gaps, wrong rotations, missing detail, asymmetry) from every side. Defaults to iso/front/left/back. This is the main way to review and iterate — do it after each modeling/te...
AI agents call screenshot_views to retrieve information from BlockbenchMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual representations of a 3D model from different perspectives. It has no side effects, creates no data modifications, executes no external code, and cannot delete or move resources. It functions as a read operation that queries the current state of the Blockbench canvas and returns image data.
From the tool's definition Tool captures and returns images/screenshots from multiple camera angles in Blockbench. It performs no modifications to the model, textures, or project state—it only retrieves visual data for review purposes.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Capture several camera angles in ONE call and return them all as images, so you can see the whole model and catch problems (gaps, wrong rotations, missing detail, asymmetry) from every side. Defaults to iso/front/left/back. This is the main way to review and iterate — do it after each modeling/texturing pass, not just once. It is categorised as a Read tool in the BlockbenchMCP MCP Server, which means it retrieves data without modifying state.
Register the Blockbench MCP server in PolicyLayer and add a rule for screenshot_views: 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 BlockbenchMCP. Nothing to install.
screenshot_views 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 screenshot_views 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 screenshot_views. 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.
screenshot_views is provided by the Blockbench MCP server (sosadly/blockbench-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 →