AI agents call list_trigger_definitions 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 enumerates predefined trigger types available in the Lönn map editor for Celeste. It is purely informational—it does not create, modify, delete, or execute any triggers or external code. The capability to list definitions is a foundational Read operation that helps users understand what options are available, with negligible risk if misused by an AI agent.
From the tool's definition Tool name is 'list_trigger_definitions' and description states 'List available Lönn trigger definitions.' The verb 'List' and the passive retrieval of available definitions indicates a query operation with no data modification, deletion, or execution of…
Attacks that exploit this kind of access
List available Lönn trigger definitions. 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 list_trigger_definitions: 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.
list_trigger_definitions 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 list_trigger_definitions 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 list_trigger_definitions. 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.
list_trigger_definitions 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 →