start_environment · QIT MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_environment does on QIT MCP Server

AI agents invoke start_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 start_environment needs a policy

This tool executes infrastructure operations (environment creation) whose effects depend on arguments and cannot be trivially undone without explicit cleanup. While the environment is described as 'temporary' and 'ephemeral,' the act of provisioning it is an Execute-category action—it runs a process that sets up system state.

From the tool's definition Tool description states it 'Start[s] a local QIT test environment' and 'Creates a temporary, ephemeral environment for testing.' Starting an environment is an operational action that triggers external system setup and configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_environment Rate-limited

start_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": {
    "start_environment": {
      "limits": [
        {
          "counter": "start_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 start_environment

What does the start_environment tool do? +

Start a local QIT test environment. Creates a temporary, ephemeral environment for testing. 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 start_environment? +

Register the QIT MCP Server MCP server in PolicyLayer and add a rule for start_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 start_environment? +

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

Can I rate-limit start_environment? +

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

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

start_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.