Clear all cells in a TileMap layer.
AI agents call tilemap_clear to permanently remove resources in Godot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes all cells from a TileMap layer, destroying the game designer's tile layout work. While scoped to a single layer, the complete and permanent removal of that layer's content qualifies as destructive. An AI agent misusing this could delete significant game level design, requiring manual reconstruction.
From the tool's definition Tool name 'tilemap_clear' and description 'Clear all cells in a TileMap layer' indicate irreversible deletion of all tile data in a layer without restoration mechanism.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all cells in a TileMap layer. It is categorised as a Destructive tool in the Godot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for tilemap_clear: 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 Server. Nothing to install.
tilemap_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tilemap_clear 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_clear. 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_clear is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). 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 →