plugin_install

Install a software/plugin.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aapanel-mcp/plugin-install.md

WHAT IT DOES

What plugin_install does on Aapanel

AI agents invoke plugin_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.

RISK

Why plugin_install is rated High

Installing software/plugins executes installation processes on the server, modifying the system state by adding new software. This is more than a simple write operation as it involves executing code and potentially modifying system configurations. Misuse could install malicious plugins or unwanted software on the server.

From the tool's definition Install a software/plugin

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs plugin_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 plugin_install, this is the rule to start with:

plugin_install Rate-limited

plugin_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "plugin_install": {
      "limits": [
        {
          "counter": "plugin_install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every plugin_install call is checked against it from then on.

FAQ

Questions about plugin_install

What does the plugin_install tool do? +

Install a software/plugin. 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.

How do I enforce a policy on plugin_install? +

Register the Aapanel MCP server in PolicyLayer and add a rule for plugin_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.

What risk level is plugin_install? +

plugin_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit plugin_install? +

Yes. Add a rate_limit block to the plugin_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.

How do I block plugin_install completely? +

Set action: deny in the PolicyLayer policy for plugin_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.

What MCP server provides plugin_install? +

plugin_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.

KEEP EXPLORING

More on Aapanel, and thousands of servers like it.

This server

All 282 Aapanel tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →