get_editor_screenshot
Take a screenshot of the Godot editor window
This record as markdown: /tools/keeveeg-godot-mcp/get-editor-screenshot.md
What get_editor_screenshot does on Godot
AI agents call get_editor_screenshot to retrieve information from Godot 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 |
|---|---|---|---|
path | string | — | Custom save path for the screenshot |
Parameters from the server's own tool schema.
Why get_editor_screenshot is rated Low
This tool retrieves/queries visual data from the Godot editor interface. It has no side effects, creates no persistent changes, executes no code, and poses minimal risk—it merely captures and returns what is currently displayed on screen. Classification as Read is appropriate.
From the tool's definition Tool name 'get_editor_screenshot' and description 'Take a screenshot of the Godot editor window' indicate a read-only operation that captures visual state without modifying or executing anything.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_editor_screenshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_editor_screenshot, this is the rule to start with:
get_editor_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 Godot, apply this rule, and every get_editor_screenshot call is checked against it from then on.
Questions about get_editor_screenshot
Take a screenshot of the Godot editor window. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_editor_screenshot accepts 1 parameter: path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for get_editor_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 Godot. Nothing to install.
get_editor_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_editor_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_editor_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_editor_screenshot is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue