install_application
Install an application on a hosting package
This record as markdown: /tools/cbrown35-20i-mcp/install-application.md
What install_application does on 20i MCP Server
AI agents invoke install_application to trigger actions in 20i MCP Server. 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.
Why install_application is rated High
Installing an application triggers an external operation that modifies the hosting environment by deploying software. This goes beyond a simple write (data creation/modification) as it executes an installation process with side effects that depend on the application being installed. Misuse could result in malicious or unwanted software being deployed on a hosting package, hence high severity.
From the tool's definition Install an application on a hosting package
Attacks that exploit this kind of access
The rule that runs install_application safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install_application, this is the rule to start with:
install_application stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every install_application call is checked against it from then on.
Questions about install_application
Install an application on a hosting package. It is categorised as a Execute tool in the 20i MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for install_application: 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 20i MCP Server. Nothing to install.
install_application 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_application 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_application. 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_application is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue