AI agents use resize_room 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 modifies map file structure by changing room dimensions—a write operation. It is not destructive because data is preserved and the operation is reversible (a room can be resized again). It is not execute/financial/other. Severity is medium because misconfiguration could corrupt map layouts or make rooms unusable, but the effect is confined to a single map file and can be undone.
From the tool's definition Tool description states it resizes a room and 'preserves tile data', indicating modification of room dimensions in the .bin map file. The name 'resize_room' and verb 'Resize' confirm a mutative operation.
Attacks that exploit this kind of access
Resize a room (snaps to 8-pixel grid, preserves tile data). 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 resize_room: 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.
resize_room 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 resize_room 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 resize_room. 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.
resize_room 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 →