AI agents invoke install_loenn_manager to trigger actions in Loenn. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name strongly implies installing software or a manager component, which would constitute executing an external operation with potentially broad system effects. However, with no description available, confidence is low. Installation operations typically fall under Execute as they run processes and modify system state, warranting a high severity due to the potential blast radius of installing unintended software.
From the tool's definition Tool name 'install_loenn_manager' — the word 'install' implies executing an installation process, but the description is empty and uninformative.
Attacks that exploit this kind of access
install_loenn_manager. It is categorised as a Execute tool in the Loenn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Loenn MCP server in PolicyLayer and add a rule for install_loenn_manager: 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.
install_loenn_manager is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the install_loenn_manager 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 install_loenn_manager. 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.
install_loenn_manager 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 →