project_start

What project_start does on Aapanel

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

Starting a project is an executable action that initiates processes or services in the underlying system. This is not a read operation (no data retrieval), not destructive (reversible via project_stop), and not financial. It qualifies as Execute because it triggers external operations with effects dependent on arguments.

From the tool's definition Tool name 'project_start' indicates execution of a project startup action. In a panel management context (aaPanel), this triggers external operational effects (starting services, processes, or applications) whose outcomes depend on which project is targeted.

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

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

Questions about project_start