Add a Camera3D node to the scene with optional configuration.
AI agents use setup_camera_3d to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
The tool creates a new Camera3D node in the scene, which modifies the game project state reversibly. While this alters the project, the change can be undone (deleted) without data loss or permanent damage. It does not execute arbitrary code, delete existing data, or move funds. The blast radius is medium because misconfigured cameras could affect game logic or rendering, but the change is easily reverted.
From the tool's definition Tool name 'setup_camera_3d' and description 'Add a Camera3D node to the scene' indicate creation of a new node in the Godot scene tree.
Attacks that exploit this kind of access
Add a Camera3D node to the scene with optional configuration. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for setup_camera_3d: 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 Server. Nothing to install.
setup_camera_3d is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setup_camera_3d 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.
Set action: deny in the PolicyLayer policy for setup_camera_3d. 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.
setup_camera_3d is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →