editor_set_camera · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_set_camera does on Godot

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

PARAMETERS

Parameter	Type	Required	Description
`position`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_set_camera needs a policy

This tool modifies the editor viewport camera position, which is a reversible write operation affecting only the editor view state. It does not delete data, execute code, or have financial implications. The blast radius is low as it only changes where the editor camera is pointed.

From the tool's definition Set the 3D editor viewport camera position

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_set_camera Rate-limited

editor_set_camera 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": {
    "editor_set_camera": {
      "limits": [
        {
          "counter": "editor_set_camera_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, so you can run agents against it safely.

FAQ

Questions about editor_set_camera

What does the editor_set_camera tool do? +

Set the 3D editor viewport camera position. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does editor_set_camera accept? +

editor_set_camera accepts 1 parameter: position. Required: position. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_set_camera? +

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

What risk level is editor_set_camera? +

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

Can I rate-limit editor_set_camera? +

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

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

editor_set_camera is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.