This record as markdown: /tools/chanceflow-godot-mcp/camera-set-properties.md
What camera_set_properties does on Godot
AI agents use camera_set_properties 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.
Why camera_set_properties is rated Medium
This tool creates or modifies data (camera properties) within the Godot scene/project, making it a Write operation. The severity is medium because misuse could disrupt game visuals or camera behavior, but changes are reversible.
From the tool's definition Tool name 'camera_set_properties' indicates modification of camera object properties. Within a Godot game engine context, setting properties modifies scene state.
Attacks that exploit this kind of access
The rule that runs camera_set_properties 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_properties, this is the rule to start with:
camera_set_properties 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 camera_set_properties call is checked against it from then on.
Questions about camera_set_properties
camera_set_properties 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.
Register the Godot MCP server in PolicyLayer and add a rule for camera_set_properties: 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.
camera_set_properties 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 camera_set_properties 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 camera_set_properties. 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.
camera_set_properties 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue