AI agents use import_room_json 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.
Import operations create or modify data structures (rooms in this case) within map files. This is reversible (can be undone or re-imported), distinguishing it from Destructive. However, the empty description limits confidence—it could potentially have Execute-like properties if import validation/parsing is unsafe.
From the tool's definition Tool name 'import_room_json' with context of Celeste .bin map file editing; sibling tools include 'add_room', 'add_entity', 'add_trigger' which are clearly Write operations.
Attacks that exploit this kind of access
import_room_json. 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 import_room_json: 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.
import_room_json 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 import_room_json 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 import_room_json. 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.
import_room_json 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 →