simulate_key · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What simulate_key does on Godot MCP Server

AI agents invoke simulate_key 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 simulate_key needs a policy

This tool injects synthetic keyboard input into a running game, triggering in-game actions whose effects depend entirely on the key simulated and the game's current state. It causes real side effects (game state changes, triggered mechanics) and could be misused to trigger unintended game behaviors. It fits Execute as it performs an external operation with context-dependent outcomes.

From the tool's definition Simulate a keyboard key event in the running game

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulate_key Rate-limited

simulate_key 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": {
    "simulate_key": {
      "limits": [
        {
          "counter": "simulate_key_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 simulate_key

What does the simulate_key tool do? +

Simulate a keyboard key event in 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 simulate_key? +

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

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

Can I rate-limit simulate_key? +

Yes. Add a rate_limit block to the simulate_key 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 simulate_key completely? +

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

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