stop_local_site · LocalWP MCP: Risk & Policy

WHAT IT DOES

What stop_local_site does on LocalWP MCP

AI agents invoke stop_local_site to trigger actions in LocalWP MCP. 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 IT NEEDS A POLICY

Why stop_local_site needs a policy

This tool executes an external operation (stopping services) rather than merely reading or writing data. While not destructive (services can be restarted), it interrupts running operations and affects system state in a way that depends on the argument (which site is selected).

From the tool's definition Tool explicitly 'Stops the selected LocalWP site and all of its services' - a direct action that triggers external operations (service shutdown) with effects dependent on which site is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_local_site Rate-limited

stop_local_site 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": {
    "stop_local_site": {
      "limits": [
        {
          "counter": "stop_local_site_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LocalWP MCP, so you can run agents against it safely.

FAQ

Questions about stop_local_site

What does the stop_local_site tool do? +

Stops the selected LocalWP site and all of its services. It is categorised as a Execute tool in the LocalWP MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_local_site? +

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

What risk level is stop_local_site? +

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

Can I rate-limit stop_local_site? +

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

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

stop_local_site is provided by the LocalWP MCP server (kazimshah39/localwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.