start_frame_capture · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_frame_capture does on Godot MCP Server

AI agents invoke start_frame_capture to trigger actions in Godot MCP Server. 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.

WHY IT NEEDS A POLICY

Why start_frame_capture needs a policy

This tool initiates a continuous capture process on a running Godot game instance. It executes an operation that affects a live external process (the game), making it Execute category. It is not purely reading data (it starts an active capture loop) and has no destructive or financial implications. Misuse could cause performance degradation or interfere with the running game, warranting medium severity.

From the tool's definition 'Start continuous frame capture from the running game' — triggers an ongoing external operation against a live game process via WebSocket

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_frame_capture Rate-limited

start_frame_capture 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_frame_capture": {
      "limits": [
        {
          "counter": "start_frame_capture_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about start_frame_capture

What does the start_frame_capture tool do? +

Start continuous frame capture from the running game. It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_frame_capture? +

Register the Godot MCP Server MCP server in PolicyLayer and add a rule for start_frame_capture: 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.

What risk level is start_frame_capture? +

start_frame_capture is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_frame_capture? +

Yes. Add a rate_limit block to the start_frame_capture 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.

How do I block start_frame_capture completely? +

Set action: deny in the PolicyLayer policy for start_frame_capture. 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.

What MCP server provides start_frame_capture? +

start_frame_capture 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.