run_test_group · QIT MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_test_group does on QIT MCP Server

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

This tool executes pre-defined test suites against WordPress/WooCommerce plugins. While tests are typically read-only in intent, they are Execute-category because: (1) they trigger external code execution, (2) test behavior depends on which tests are selected/run, and (3) in a plugin testing context, tests may modify test environments or plugin state.

From the tool's definition The tool 'run_test_group' executes a group of tests defined in a configuration file. Testing operations run code and trigger external operations whose effects depend on arguments (test selection, environment state).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_test_group Rate-limited

run_test_group 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": {
    "run_test_group": {
      "limits": [
        {
          "counter": "run_test_group_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 run_test_group

What does the run_test_group tool do? +

Run a group of tests defined in qit.json configuration file. 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 run_test_group? +

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

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

Can I rate-limit run_test_group? +

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

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

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