This record as markdown: /tools/yanhuifair-godot-mcp/create-curve.md
What create_curve does on Godot
AI agents use create_curve 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 | Output path (e.g. "curves/ease_in.tres") |
points | object | — | Array of [x, y] control points |
bake_resolution | object | — | Bake resolution |
Parameters from the server's own tool schema.
Why create_curve is rated Medium
The tool creates a new Curve resource file, which is a Write operation - it creates data that can be modified or deleted later. It does not execute arbitrary code, delete data irreversibly, or affect financial systems. The severity is medium because creating or modifying project resources could impact game functionality if an AI agent generates malformed curves, but the effect is containable and reversible.
From the tool's definition Tool name 'create_curve' combined with description 'Create Curve .tres' indicates creation of a new resource file (.tres is Godot's text-based resource format). This is a reversible data creation operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_curve 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 create_curve, this is the rule to start with:
create_curve 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 create_curve call is checked against it from then on.
Questions about create_curve
Create Curve .tres. 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.
create_curve accepts 3 parameters: path, points, bake_resolution. Required: path. 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 create_curve: 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.
create_curve 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 create_curve 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 create_curve. 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.
create_curve 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue