soft_install
Install a software component (nginx, apache, mysql, php, redis, etc.).
This record as markdown: /tools/aapanel-mcp/soft-install.md
What soft_install does on Aapanel
AI agents invoke soft_install to trigger actions in Aapanel. 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 soft_install is rated High
Installing software triggers external operations on the server — downloading packages, running installation scripts, modifying system configuration, and potentially starting new services. This is a privileged system-level operation with significant blast radius if misused (e.g., installing unintended or malicious software, changing server configuration).
From the tool's definition Install a software component (nginx, apache, mysql, php, redis, etc.)
Attacks that exploit this kind of access
The rule that runs soft_install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For soft_install, this is the rule to start with:
soft_install 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 Aapanel, apply this rule, and every soft_install call is checked against it from then on.
Questions about soft_install
Install a software component (nginx, apache, mysql, php, redis, etc.). It is categorised as a Execute tool in the Aapanel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aapanel MCP server in PolicyLayer and add a rule for soft_install: 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 Aapanel. Nothing to install.
soft_install 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 soft_install 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 soft_install. 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.
soft_install is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue