This record as markdown: /tools/keeveeg-godot-mcp/tilemap-set-cell.md
What tilemap_set_cell does on Godot
AI agents use tilemap_set_cell 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 | TileMap node path |
coords | array | Yes | Integer coordinates [x, y] |
source_id | integer | — | TileSet source ID |
atlas_coords | object | — | Atlas coordinates [x, y] |
alternative_tile | integer | — | Alternative tile ID |
Parameters from the server's own tool schema.
Why tilemap_set_cell is rated Medium
This tool creates or modifies game scene data (a TileMap cell) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or handle finances. The severity is medium because misuse could alter game level design or create unexpected gameplay, but changes can be undone by setting cells to different values.
From the tool's definition Tool name 'tilemap_set_cell' with description 'Set a single cell in a TileMap' indicates modification of game scene data. The verb 'set' combined with context of modifying a TileMap cell is a reversible write operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs tilemap_set_cell 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 tilemap_set_cell, this is the rule to start with:
tilemap_set_cell 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 tilemap_set_cell call is checked against it from then on.
Questions about tilemap_set_cell
Set a single cell in a TileMap. 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.
tilemap_set_cell accepts 5 parameters: path, coords, source_id, atlas_coords, alternative_tile. Required: path, coords. 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 tilemap_set_cell: 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.
tilemap_set_cell 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 tilemap_set_cell 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 tilemap_set_cell. 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.
tilemap_set_cell is provided by the Godot MCP server (@keeveeg/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