screenshot_editor
Capture the 2D or 3D editor viewport as a PNG and return it as image content so the assistant can see the scene. Requires the matching editor tab (2D/3D) to be active and rendered.
This record as markdown: /tools/breakpoint-mcp/screenshot-editor.md
What screenshot_editor does on Breakpoint
AI agents call screenshot_editor to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
viewport | string | — | Which viewport (default 3d) |
Parameters from the server's own tool schema.
Why screenshot_editor is rated Low
This tool retrieves visual state information from the active editor tab and returns it without modifying any underlying data, state, or project files. It is a passive observation operation similar to querying or fetching, with no irreversible consequences, code execution, or resource-consuming operations.
From the tool's definition Tool captures and returns a screenshot of the editor viewport as image content. The verb 'Capture' and 'return' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs screenshot_editor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screenshot_editor, this is the rule to start with:
screenshot_editor is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every screenshot_editor call is checked against it from then on.
Questions about screenshot_editor
Capture the 2D or 3D editor viewport as a PNG and return it as image content so the assistant can see the scene. Requires the matching editor tab (2D/3D) to be active and rendered. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
screenshot_editor accepts 1 parameter: viewport. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for screenshot_editor: 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 Breakpoint. Nothing to install.
screenshot_editor 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_editor 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_editor. 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_editor is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue