New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

tilemap_set_cells_rect

Paint every cell in a rectangular region of a TileMapLayer with one tile (undoable, one action). source_id -1 clears the region. Capped at 65536 cells; split larger fills across calls.

SERVERBreakpoint SOURCEbreakpoint-mcp
Medium RISK CLASS
Category Write
Parameters 52 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/tilemap-set-cells-rect.md

What tilemap_set_cells_rect does on Breakpoint

AI agents use tilemap_set_cells_rect to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.

ParameterTypeRequiredDescription
path string Yes TileMapLayer node path relative to the scene root
rect array Yes Region [x, y, width, height] in cells (width/height > 0)
source_id integer Atlas source id from the bound TileSet, or -1 to clear (default -1)
alternative integer Alternative tile id (default 0)
atlas_coords array Tile atlas coordinates [x, y] within the source (default [0, 0])

Parameters from the server's own tool schema.

Why tilemap_set_cells_rect is rated Medium

This tool modifies tilemap data by painting cells in a rectangular region. While it can clear cells (source_id -1), the emphasis on 'undoable' means changes are reversible, placing it in Write rather than Destructive. The blast radius is medium because bulk modifications to game assets could corrupt visual layouts, but the undo capability and cell count cap (65536) limit damage.

From the tool's definition 'Paint every cell in a rectangular region' and 'source_id -1 clears the region' indicate data modification. The description explicitly states '(undoable, one action)' confirming reversibility.

Risk signalsAccepts file system path (path) · Bulk/mass operation — affects multiple targets

Questions about tilemap_set_cells_rect

What does the tilemap_set_cells_rect tool do? +

Paint every cell in a rectangular region of a TileMapLayer with one tile (undoable, one action). source_id -1 clears the region. Capped at 65536 cells; split larger fills across calls. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does tilemap_set_cells_rect accept? +

tilemap_set_cells_rect accepts 5 parameters: path, rect, source_id, alternative, atlas_coords. Required: path, rect. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tilemap_set_cells_rect? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for tilemap_set_cells_rect: 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 Breakpoint. Nothing to install.

What risk level is tilemap_set_cells_rect? +

tilemap_set_cells_rect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tilemap_set_cells_rect? +

Yes. Add a rate_limit block to the tilemap_set_cells_rect 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.

How do I block tilemap_set_cells_rect completely? +

Set action: deny in the PolicyLayer policy for tilemap_set_cells_rect. 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.

What MCP server provides tilemap_set_cells_rect? +

tilemap_set_cells_rect is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Breakpoint, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.