execute_test · Qontinui MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_test does on Qontinui MCP Server

AI agents invoke execute_test to trigger actions in Qontinui 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 execute_test needs a policy

This tool executes a test workflow by ID, which triggers external automation operations on visual displays. While tests are typically designed to be non-destructive verifications, the execution of visual automation workflows can produce side effects (screenshots, state changes, interactions with external systems).

From the tool's definition Tool description states "Execute a verification test by ID" with capability to return "execution result including pass/fail status, output, assertions, and screenshots." The server enables "execute visual automation workflows" which involves running external…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_test Rate-limited

execute_test 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": {
    "execute_test": {
      "limits": [
        {
          "counter": "execute_test_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 Qontinui MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_test

What does the execute_test tool do? +

Execute a verification test by ID. Returns execution result including pass/fail status, output, assertions, and screenshots. It is categorised as a Execute tool in the Qontinui 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 execute_test? +

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

What risk level is execute_test? +

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

Can I rate-limit execute_test? +

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

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

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