setup_state_machine · Godot MCP Unified MCP: Risk & Policy

WHAT IT DOES

What setup_state_machine does on Godot MCP Unified

AI agents use setup_state_machine to create or update resources in Godot MCP Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Unified environment.

WHY IT NEEDS A POLICY

Why setup_state_machine needs a policy

This tool creates or modifies game animation state machine configurations reversibly. While it affects game behavior, changes to state machine setup can be undone in Godot's editor (undo/redo) and do not delete data or execute arbitrary code. It fits the Write category as it configures/modifies game assets.

From the tool's definition Tool name 'setup_state_machine' and description 'Configure an AnimationNodeStateMachine with states and transitions' indicate creating or modifying animation state machine configuration in Godot Engine.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_state_machine Rate-limited

setup_state_machine stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_state_machine": {
      "limits": [
        {
          "counter": "setup_state_machine_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Unified, so you can run agents against it safely.

FAQ

Questions about setup_state_machine

What does the setup_state_machine tool do? +

Configure an AnimationNodeStateMachine with states and transitions for animation control. It is categorised as a Write tool in the Godot MCP Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_state_machine? +

Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for setup_state_machine: 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 Unified. Nothing to install.

What risk level is setup_state_machine? +

setup_state_machine is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_state_machine? +

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

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

setup_state_machine is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.