setup_environment · Godot MCP Unified MCP: Risk & Policy

WHAT IT DOES

What setup_environment does on Godot MCP Unified

AI agents use setup_environment 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_environment needs a policy

This tool creates and configures an Environment resource, which is a reversible modification to scene configuration. It does not delete data (not Destructive), execute arbitrary code (not Execute), handle financial operations (not Financial), or merely retrieve data (not Read). Creating scene resources is a standard Write operation in game development.

From the tool's definition Tool name 'setup_environment' and description 'Create an Environment resource' indicate creation of a new resource that modifies 3D scene settings (lighting, fog, post-processing). The verb 'Create' is characteristic of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_environment Rate-limited

setup_environment 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_environment": {
      "limits": [
        {
          "counter": "setup_environment_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_environment

What does the setup_environment tool do? +

Create an Environment resource for 3D scene settings (lighting, fog, post-processing). 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_environment? +

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

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

Can I rate-limit setup_environment? +

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

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

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