Set a single tile in a TileMapLayer at a specified grid position
AI agents use set_tile to create or update resources in Godot MCP Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Unified environment.
This tool modifies game level data by placing or changing a tile at a specific grid position in a TileMapLayer. This is a reversible write operation—tiles can be changed or removed later. While it affects game state, it does not execute arbitrary code, delete data irreversibly, or trigger financial transactions.
From the tool's definition Tool name 'set_tile' and description 'Set a single tile in a TileMapLayer at a specified grid position' indicates modification of tilemap data.
Attacks that exploit this kind of access
Set a single tile in a TileMapLayer at a specified grid position. It is categorised as a Write tool in the Godot MCP Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for set_tile: 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 MCP Unified. Nothing to install.
set_tile 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 set_tile 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 set_tile. 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.
set_tile is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →