capture_frames
🔴 Game must be running. Capture frames from the running game viewport as PNG files
This record as markdown: /tools/keeveeg-godot-mcp/capture-frames.md
What capture_frames does on Godot
AI agents invoke capture_frames to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | integer | — | Number of frames to capture (default: 1) |
interval | number | — | Interval between captures in seconds |
Parameters from the server's own tool schema.
Why capture_frames is rated High
This tool captures frames from a running game and writes PNG files to disk. It requires an active game process ('Game must be running') and triggers an external operation (capturing viewport data and writing files). It spans Write (creating files) and Execute (interacting with a running process/viewport), so Execute is the most appropriate category.
From the tool's definition Capture frames from the running game viewport as PNG files
Attacks that exploit this kind of access
The rule that runs capture_frames 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_frames, this is the rule to start with:
capture_frames stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_frames call is checked against it from then on.
Questions about capture_frames
🔴 Game must be running. Capture frames from the running game viewport as PNG files. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
capture_frames accepts 2 parameters: count, interval. 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_frames: 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_frames is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the capture_frames 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_frames. 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_frames 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.
Across the catalogue