This record as markdown: /tools/keeveeg-godot-mcp/setup-camera-3d.md
What setup_camera_3d does on Godot
AI agents use setup_camera_3d 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Camera node path |
properties | object | Yes | Camera properties (fov, near, far, position, look_at, make_current, etc.) |
Parameters from the server's own tool schema.
Why setup_camera_3d is rated Medium
This tool creates and configures a Camera3D node within a Godot project, which is a reversible operation. It modifies project state by adding a scene node, but the changes can be undone. There is no code execution, data deletion, or external system interaction. This falls clearly under Write category as it creates/modifies data reversibly within the game editor context.
From the tool's definition Tool name 'setup_camera_3d' and description 'Add and configure a Camera3D node' indicate creation and modification of a scene node in Godot engine.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs setup_camera_3d 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 setup_camera_3d, this is the rule to start with:
setup_camera_3d 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every setup_camera_3d call is checked against it from then on.
Questions about setup_camera_3d
Add and configure a Camera3D node. 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.
setup_camera_3d accepts 2 parameters: path, properties. Required: path, properties. The full parameter table on this page comes from the server's own tool schema.
Register the Godot 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. 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 (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue