AI agents call get_map_dependencies 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.
This tool retrieves metadata about mod dependencies from configuration files. It performs a read-only query operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an agent could only learn about dependency information already present in the map file.
From the tool's definition Tool name includes 'get_' prefix and description explicitly states 'Read the mod dependencies list' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Read the mod dependencies list from a map's everest.yaml or meta node. 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 get_map_dependencies: 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.
get_map_dependencies 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 get_map_dependencies 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 get_map_dependencies. 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.
get_map_dependencies 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 →