This record as markdown: /tools/yanhuifair-godot-mcp/capture-screenshot.md
What capture_screenshot does on Godot
AI agents call capture_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 |
|---|---|---|---|
delay | object | — | Delay in seconds before capture |
output_path | object | — | Output file path for the screenshot |
window_title | object | — | Window title to capture (default: capture Godot window) |
Parameters from the server's own tool schema.
Why capture_screenshot is rated Low
Taking a screenshot reads/captures the current visual state of the running game without modifying any data or state. It is a read operation with minimal blast radius.
From the tool's definition Capture screenshot of running game
Attacks that exploit this kind of access
The rule that runs capture_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 capture_screenshot, this is the rule to start with:
capture_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 capture_screenshot call is checked against it from then on.
Questions about capture_screenshot
Capture screenshot of running game. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
capture_screenshot accepts 3 parameters: delay, output_path, window_title. 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 capture_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.
capture_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 capture_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 capture_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.
capture_screenshot is provided by the Godot MCP server (@yanhuifair/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