stop_task · Task MCP: Risk & Policy

WHAT IT DOES

What stop_task does on Task

AI agents use stop_task to create or update resources in Task — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Task environment.

WHY IT NEEDS A POLICY

Why stop_task needs a policy

This tool pauses an active timer on a task but keeps the claim intact. It modifies the task's state (from active/started to stopped/paused) in a reversible way — the task can be restarted. No data is deleted, no code is executed, and no financial operations are involved. This is a Write operation with low severity since it only affects task timing state.

From the tool's definition Stop working on a task (pauses active timer, keeps claim)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_task Rate-limited

stop_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_task": {
      "limits": [
        {
          "counter": "stop_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Task, so you can run agents against it safely.

FAQ

Questions about stop_task

What does the stop_task tool do? +

Stop working on a task (pauses active timer, keeps claim). It is categorised as a Write tool in the Task MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on stop_task? +

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

What risk level is stop_task? +

stop_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit stop_task? +

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

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

stop_task is provided by the Task MCP server (maxronner/taskwarrior-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.