task_stop · Semaphore MCP: Risk & Policy

WHAT IT DOES

What task_stop does on Semaphore

AI agents invoke task_stop to trigger actions in Semaphore. 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 task_stop needs a policy

Stopping a running task triggers an external operation with real-world effects—it halts ongoing infrastructure automation, potentially leaving systems in intermediate states or disrupting deployments. This is an Execute action (not Destructive, as the task itself isn't permanently deleted or data erased).

From the tool's definition Stops a running task in Semaphore automation workflows (Ansible, Terraform, etc.). The description indicates an action that interrupts an actively executing process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_stop Rate-limited

task_stop 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": {
    "task_stop": {
      "limits": [
        {
          "counter": "task_stop_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 Semaphore, so you can run agents against it safely.

FAQ

Questions about task_stop

What does the task_stop tool do? +

Stop a running task. It is categorised as a Execute tool in the Semaphore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on task_stop? +

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

What risk level is task_stop? +

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

Can I rate-limit task_stop? +

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

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

task_stop is provided by the Semaphore MCP server (vitexsoftware/semaphore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.