Remove an entity from a room by its ID.
AI agents call remove_entity to permanently remove resources in Loenn — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a named entity from a Celeste map room. This is a destructive write with no indication of reversibility; misuse by an AI agent could corrupt or significantly alter map structure, losing authored content.
From the tool's definition 'Remove an entity from a room by its ID' — removing a map entity is a destructive operation that deletes data from the map file irreversibly (unless a separate undo mechanism exists, which is not mentioned).
Attacks that exploit this kind of access
Remove an entity from a room by its ID. It is categorised as a Destructive tool in the Loenn MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Loenn MCP server in PolicyLayer and add a rule for remove_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.
remove_entity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
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 →