stop_environment · QIT MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_environment does on QIT MCP Server

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

WHY IT NEEDS A POLICY

Why stop_environment needs a policy

This tool executes a command against a QIT test environment infrastructure. While reversible (environments can be restarted), it is an operational execution that modifies system state rather than merely reading data. Severity is medium because misuse could disrupt testing workflows but does not permanently destroy data or commit financial obligations.

From the tool's definition Tool performs 'stop a running QIT test environment'—an operational action that triggers external system state changes (halting a running service/container).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_environment Rate-limited

stop_environment 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_environment": {
      "limits": [
        {
          "counter": "stop_environment_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 QIT MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_environment

What does the stop_environment tool do? +

Stop a running QIT test environment. It is categorised as a Execute tool in the QIT 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 stop_environment? +

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

What risk level is stop_environment? +

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

Can I rate-limit stop_environment? +

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

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

stop_environment is provided by the QIT MCP Server MCP server (woocommerce/qit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.