create_camera_attributes · Godot MCP: Risk & Policy

WHAT IT DOES

What create_camera_attributes does on Godot

AI agents use create_camera_attributes 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
`path`	string	Yes
`preset`	object	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why create_camera_attributes needs a policy

This tool creates camera attribute resources (Practical or Physical) for depth-of-field and auto-exposure settings. Creation of engine resources is a reversible Write operation—the attributes can be modified or deleted. There is no destructive data loss, code execution, or external side effects beyond configuring camera rendering parameters within the game engine environment.

From the tool's definition Tool name is 'create_camera_attributes' and description states 'Create CameraAttributes', indicating creation of new camera configuration objects in Godot Engine.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_camera_attributes Rate-limited

create_camera_attributes 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": {
    "create_camera_attributes": {
      "limits": [
        {
          "counter": "create_camera_attributes_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 create_camera_attributes

What does the create_camera_attributes tool do? +

Create CameraAttributes (Practical or Physical) for 3D camera DOF and auto-exposure. 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 create_camera_attributes accept? +

create_camera_attributes accepts 2 parameters: path, preset. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_camera_attributes? +

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

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

Can I rate-limit create_camera_attributes? +

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

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

create_camera_attributes 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.