record_gameplay
Record gameplay for a duration, capturing input events and/or game state
This record as markdown: /tools/keeveeg-godot-mcp/record-gameplay.md
What record_gameplay does on Godot
AI agents invoke record_gameplay 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 |
|---|---|---|---|
duration | number | — | Recording duration in seconds (default: 10) |
include_input | boolean | — | Record input events (default: true) |
include_state | boolean | — | Record game state snapshots (default: false) |
Parameters from the server's own tool schema.
Why record_gameplay is rated High
This tool actively runs a recording process within the Godot game engine, capturing input events and game state over time. It triggers an external operation (gameplay recording) that depends on arguments like duration and what to capture. It is not merely reading static data — it initiates an active process that interacts with the running game engine, placing it in the Execute category.
From the tool's definition Record gameplay for a duration, capturing input events and/or game state
Attacks that exploit this kind of access
The rule that runs record_gameplay 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 record_gameplay, this is the rule to start with:
record_gameplay 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 record_gameplay call is checked against it from then on.
Questions about record_gameplay
Record gameplay for a duration, capturing input events and/or game state. 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.
record_gameplay accepts 3 parameters: duration, include_input, include_state. 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 record_gameplay: 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.
record_gameplay 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 record_gameplay 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 record_gameplay. 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.
record_gameplay 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