Capture a screenshot of the Godot editor window.
AI agents call get_editor_screenshot to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual information (a screenshot) from the editor interface without creating, modifying, deleting, or executing any game code or external operations. It is purely observational and informational, matching the Read category profile of querying/fetching data with no side effects.
From the tool's definition Tool name 'get_editor_screenshot' and description 'Capture a screenshot of the Godot editor window' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Capture a screenshot of the Godot editor window. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server 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 MCP Server. 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 MCP server (neondeex/godotmcp-pro-free-client). 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 →