runtime_screenshot
Capture the current game frame as a PNG and return it as image content so the assistant can see the running game.
This record as markdown: /tools/breakpoint-mcp/runtime-screenshot.md
What runtime_screenshot does on Breakpoint
AI agents call runtime_screenshot 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 |
|---|---|---|---|
peer | string | — | Headless peer id from runtime_spawn_peers; omit for the default running game. |
Parameters from the server's own tool schema.
Why runtime_screenshot is rated Low
This tool only reads and captures the current visual state of the running Godot game without altering any data, code, or game logic. It is a passive observation mechanism analogous to a screenshot function, which is clearly a Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'Capture the current game frame as a PNG and return it as image content' — a retrieval operation with no modification or side effects on game state.
Attacks that exploit this kind of access
The rule that runs runtime_screenshot 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 runtime_screenshot, this is the rule to start with:
runtime_screenshot 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 runtime_screenshot call is checked against it from then on.
Questions about runtime_screenshot
Capture the current game frame as a PNG and return it as image content so the assistant can see the running game. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
runtime_screenshot accepts 1 parameter: peer. 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 runtime_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 Breakpoint. Nothing to install.
runtime_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 runtime_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 runtime_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.
runtime_screenshot 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