setup_rigidbody · Godot MCP Unified MCP: Risk & Policy

WHAT IT DOES

What setup_rigidbody does on Godot MCP Unified

AI agents use setup_rigidbody 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_rigidbody needs a policy

This tool modifies the state of physics nodes by configuring their properties (mass, friction, gravity scale, constraints, etc.). This is a Write operation—it creates or updates game object configuration reversibly. It does not execute arbitrary code, delete data, or move money. While it affects runtime behavior, the changes are not destructive and can be undone through the editor or by reconfiguring.

From the tool's definition Tool name 'setup_rigidbody' and description 'Configure physics properties for a RigidBody2D or RigidBody3D node' indicate modification of node properties. The verb 'Configure' implies setting or updating existing physics parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_rigidbody Rate-limited

setup_rigidbody 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_rigidbody": {
      "limits": [
        {
          "counter": "setup_rigidbody_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_rigidbody

What does the setup_rigidbody tool do? +

Configure physics properties for a RigidBody2D or RigidBody3D node. 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_rigidbody? +

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

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

Can I rate-limit setup_rigidbody? +

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

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

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