AI agents use move_entity 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 data (entity position) reversibly within the .bin map structure. Changes can be undone (e.g., by moving the entity back or using undo functionality), making it Write rather than Destructive. The blast radius is medium because incorrect entity positioning could break map logic or gameplay, but the action is not permanent and the map file itself is not deleted.
From the tool's definition Tool name 'move_entity' and description 'Move an entity to a new position' indicate modification of entity coordinates/properties within a Celeste map file.
Attacks that exploit this kind of access
Move an entity to a new position. 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 move_entity: 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.
move_entity 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 move_entity 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 move_entity. 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.
move_entity 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.
move_entity is one line of Loenn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →