stop_execution · Qontinui MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_execution does on Qontinui MCP Server

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

This tool executes a command that interrupts an in-flight operation (workflow execution) rather than simply reading data. While stopping a process is not destructive to data (no permanent deletion), it is an active operation that changes system state and workflow behavior in real-time. Misuse could disrupt legitimate automation tasks running in production.

From the tool's definition Tool name 'stop_execution' and description 'Stop the currently running workflow execution' indicate this performs an operation that triggers external state change—halting an active visual automation workflow on the Qontinui Runner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_execution Rate-limited

stop_execution 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_execution": {
      "limits": [
        {
          "counter": "stop_execution_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 stop_execution

What does the stop_execution tool do? +

Stop the currently running workflow execution. 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 stop_execution? +

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

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

Can I rate-limit stop_execution? +

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

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

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