AI agents use add_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 map data by adding entities to Celeste .bin files. While reversible (entities can be removed), it represents a write operation that changes the game map structure. Severity is high because uncontrolled entity addition could corrupt maps or create unintended gameplay effects.
From the tool's definition Tool name 'add_entity' combined with server description stating it 'enables AI agents to read, edit, analyze, procedurally generate, and preview Celeste .bin map files'.
Attacks that exploit this kind of access
add_entity. 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 add_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.
add_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 add_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 add_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.
add_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 →