get_game_screenshot
Take a screenshot of the running game viewport
This record as markdown: /tools/keeveeg-godot-mcp/get-game-screenshot.md
What get_game_screenshot does on Godot
AI agents call get_game_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_game_screenshot is rated Low
This tool captures visual data from a running Godot game viewport. It is a read-only operation that retrieves information (a screenshot image) without modifying, deleting, executing arbitrary code, or causing financial impact. The sibling tools on this server are all Write-category tools (add_* operations), but this particular tool is distinctly observational.
From the tool's definition Tool name is 'get_game_screenshot' and description states 'Take a screenshot of the running game viewport' — a retrieval operation with no side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_game_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_game_screenshot, this is the rule to start with:
get_game_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_game_screenshot call is checked against it from then on.
Questions about get_game_screenshot
Take a screenshot of the running game viewport. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_game_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_game_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_game_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_game_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_game_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_game_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