AI agents call compare_rooms to retrieve information from Loenn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The compare_rooms tool retrieves and presents data about two rooms for analysis purposes. It performs no side effects, does not modify map data, execute code conditionally on inputs, or delete anything. This is purely informational/analytical, making it a Read category risk with low severity since misuse would only result in unwanted information disclosure about map contents.
From the tool's definition Tool description states 'Compare two rooms in the same map side-by-side' — a query/analysis operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Compare two rooms in the same map side-by-side. It is categorised as a Read tool in the Loenn MCP Server, which means it retrieves data without modifying state.
Register the Loenn MCP server in PolicyLayer and add a rule for compare_rooms: 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.
compare_rooms is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the compare_rooms 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 compare_rooms. 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.
compare_rooms 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 →