add_tileset_source
Add an atlas source (texture) to a TileSet.
This record as markdown: /tools/yanhuifair-godot-mcp/add-tileset-source.md
What add_tileset_source does on Godot
AI agents use add_tileset_source 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 |
|---|---|---|---|
margin | object | — | Atlas margin [x, y] |
source_id | object | — | Source index (auto-detected if omitted) |
tile_size | object | — | Tile size [x, y] in pixels |
separation | object | — | Atlas separation [x, y] |
texture_path | string | Yes | Path to the tileset atlas texture (e.g. "res://textures/tiles.png") |
tileset_path | string | Yes | Path to .tres TileSet file |
Parameters from the server's own tool schema.
Why add_tileset_source is rated Medium
Creates or modifies TileSet data by adding texture sources; reversible operation.
From the tool's definition Add an atlas source (texture) to a TileSet.
Attacks that exploit this kind of access
The rule that runs add_tileset_source 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 add_tileset_source, this is the rule to start with:
add_tileset_source 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 add_tileset_source call is checked against it from then on.
Questions about add_tileset_source
Add an atlas source (texture) to a TileSet. 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.
add_tileset_source accepts 6 parameters: margin, source_id, tile_size, separation, texture_path, tileset_path. Required: texture_path, tileset_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 add_tileset_source: 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.
add_tileset_source 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 add_tileset_source 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 add_tileset_source. 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.
add_tileset_source 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