site_stop

Stop a website.

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/site-stop.md

WHAT IT DOES

What site_stop does on Aapanel

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

Stopping a website is an executable action that disrupts service availability and has immediate operational consequences. It is not a read operation (no data retrieval), not a write operation (not creating/modifying data reversibly), not destructive (the site can be restarted), and not financial. It is an Execute-category tool because it runs an operation against external infrastructure.

From the tool's definition Tool name 'site_stop' with description 'Stop a website' indicates an action that halts a running service. This triggers an external operation (stopping a web service) whose effects depend on which site argument is provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

site_stop Rate-limited

site_stop 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": {
    "site_stop": {
      "limits": [
        {
          "counter": "site_stop_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 site_stop call is checked against it from then on.

FAQ

Questions about site_stop

What does the site_stop tool do? +

Stop a website. 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 site_stop? +

Register the Aapanel MCP server in PolicyLayer and add a rule for site_stop: 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 site_stop? +

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

Can I rate-limit site_stop? +

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

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

site_stop 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

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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