camera_set_current

A write tool on the Godot MCP server.

SERVERGodot SOURCEchanceflow/godot-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chanceflow-godot-mcp/camera-set-current.md

WHAT IT DOES

What camera_set_current does on Godot

AI agents use camera_set_current 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.

RISK

Why camera_set_current is rated Medium

Based on the name, this tool likely modifies scene state by designating a specific camera as the active/current camera. This is a reversible write operation — changing which camera is active can be undone by setting another camera. Confidence is reduced due to the empty description.

From the tool's definition Tool name 'camera_set_current' suggests setting a camera as the current/active camera in a scene. Description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs camera_set_current safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For camera_set_current, this is the rule to start with:

camera_set_current Rate-limited

camera_set_current 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": {
    "camera_set_current": {
      "limits": [
        {
          "counter": "camera_set_current_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every camera_set_current call is checked against it from then on.

FAQ

Questions about camera_set_current

What does the camera_set_current tool do? +

camera_set_current is a write tool on the Godot MCP server. 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.

How do I enforce a policy on camera_set_current? +

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

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

Can I rate-limit camera_set_current? +

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

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

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

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 84 Godot tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →