AI agents use set_room_tiles to create or update resources in Loenn — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Loenn environment.
This tool creates or modifies map data (room tiles) in a reversible manner. While it alters the map file, the changes can be undone (reverted to previous versions or overwritten), making it Write rather than Destructive. The severity is high because misuse could corrupt significant portions of a map's playable geometry, but the effect is constrained to tile data within a single room and remains reversible.
From the tool's definition Tool name 'set_room_tiles' and description 'Set tile data for a room' indicates the tool modifies room tile data. The description explicitly states it sets/writes tile data, which is a reversible modification to map file structure.
Attacks that exploit this kind of access
Set tile data for a room. Each row is a line of characters ('0'=air). It is categorised as a Write tool in the Loenn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Loenn MCP server in PolicyLayer and add a rule for set_room_tiles: 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 Loenn. Nothing to install.
set_room_tiles 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_room_tiles 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_room_tiles. 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_room_tiles is provided by the Loenn MCP server (magedeline/loenn-mcp). 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 →