tileset_add_source
Add a TileSetAtlasSource (backed by a Texture2D) to a TileSet .tres and re-save. DESTRUCTIVE (writes a file) — gated by confirmation. texture_region_size defaults to the TileSet
This record as markdown: /tools/godot-breakpoint-mcp/tileset-add-source.md
What tileset_add_source does on Godot Breakpoint
AI agents use tileset_add_source to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why tileset_add_source is rated Medium
The tool modifies an existing TileSet resource file by adding a new atlas source and re-saving it. While the description labels it 'DESTRUCTIVE', the actual operation is a write/update (adding data and overwriting a file), not an irreversible deletion or purge. File overwrites could overwrite prior state, but the primary action is creating/modifying content rather than deleting it.
From the tool's definition 'Add a TileSetAtlasSource (backed by a Texture2D) to a TileSet .tres and re-save' and 'writes a file — gated by confirmation'
Attacks that exploit this kind of access
The rule that runs tileset_add_source safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tileset_add_source, this is the rule to start with:
tileset_add_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 Breakpoint, apply this rule, and every tileset_add_source call is checked against it from then on.
Questions about tileset_add_source
Add a TileSetAtlasSource (backed by a Texture2D) to a TileSet .tres and re-save. DESTRUCTIVE (writes a file) — gated by confirmation. texture_region_size defaults to the TileSet. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for tileset_add_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 Breakpoint. Nothing to install.
tileset_add_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 tileset_add_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 tileset_add_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.
tileset_add_source is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue