install_plugin

Install a plugin

SERVEROPNsense MCP Server SOURCEfakebizprez/opnsense-mcp-server

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/fakebizprez-opnsense-mcp-server/install-plugin.md

WHAT IT DOES

What install_plugin does on OPNsense MCP Server

AI agents invoke install_plugin to trigger actions in OPNsense 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.

RISK

Why install_plugin is rated High

Installing a plugin executes a system-level software installation on a firewall appliance. This triggers external operations (package download, installation, system modification) that can alter system behavior, introduce new attack surfaces, or affect firewall functionality.

From the tool's definition 'Install a plugin' — installs software on the firewall system, triggering an external package installation operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs install_plugin safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OPNsense MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install_plugin, this is the rule to start with:

install_plugin Rate-limited

install_plugin 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": {
    "install_plugin": {
      "limits": [
        {
          "counter": "install_plugin_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 OPNsense MCP Server, apply this rule, and every install_plugin call is checked against it from then on.

FAQ

Questions about install_plugin

What does the install_plugin tool do? +

Install a plugin. It is categorised as a Execute tool in the OPNsense MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_plugin? +

Register the OPNsense MCP Server MCP server in PolicyLayer and add a rule for install_plugin: 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 OPNsense MCP Server. Nothing to install.

What risk level is install_plugin? +

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

Can I rate-limit install_plugin? +

Yes. Add a rate_limit block to the install_plugin 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 install_plugin completely? +

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

install_plugin is provided by the OPNsense MCP Server MCP server (fakebizprez/opnsense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OPNsense MCP Server, and thousands of servers like it.

This server

All 22 OPNsense MCP Server 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 →