system_service_admin

What system_service_admin does on Aapanel

AI agents invoke system_service_admin 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 system_service_admin is rated High

The tool directly executes administrative control over system services. While stopping/starting services is reversible (unlike deletion), it has immediate operational impact: stopping nginx disrupts web traffic, stopping mysql halts database access. This is Execute rather than Write because it invokes external operations (systemctl/service commands) with effects determined by arguments, not just data mutation.

From the tool's definition Start, stop, or restart a service (nginx, apache, mysql, etc.) - these are external service operations that trigger real-world effects on running infrastructure.

Risk signalsAdmin/system-level operation

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

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

Questions about system_service_admin