This record as markdown: /tools/yanhuifair-godot-mcp/create-atlas-texture.md
What create_atlas_texture does on Godot
AI agents use create_atlas_texture 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. "textures/sprite_atlas.tres") |
region | object | — | [x, y, w, h] region rect |
atlas_texture | string | Yes | Path to source texture |
Parameters from the server's own tool schema.
Why create_atlas_texture is rated Medium
This tool creates and persists a new texture resource file, which is a reversible write operation. While it modifies the project state by adding a new asset, it does not execute arbitrary code, delete data, or move money. It falls clearly into the Write category.
From the tool's definition Tool creates a .tres resource file (AtlasTexture asset), which writes new data to the filesystem. The name 'create' and description 'Create AtlasTexture .tres' explicitly indicate a resource creation operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_atlas_texture 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_atlas_texture, this is the rule to start with:
create_atlas_texture 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_atlas_texture call is checked against it from then on.
Questions about create_atlas_texture
Create AtlasTexture .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_atlas_texture accepts 3 parameters: path, region, atlas_texture. Required: path, atlas_texture. 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_atlas_texture: 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_atlas_texture 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_atlas_texture 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_atlas_texture. 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_atlas_texture 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