AI agents call get_trigger_definition 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 and reads trigger definition source files without executing code, modifying data, or causing irreversible changes. It is a pure read operation on game map file metadata. The blast radius is minimal—disclosure of source code carries low risk in the context of game modding tools.
From the tool's definition Tool name 'get_trigger_definition' and description 'Read the source of a Lönn trigger definition .lua file' explicitly indicate retrieval of source code with no modification or side effects.
Attacks that exploit this kind of access
Read the source of a Lönn trigger definition .lua file. 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_trigger_definition: 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_trigger_definition 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_trigger_definition 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_trigger_definition. 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_trigger_definition 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 →