taskwarrior_start · Taskwarrior MCP Server MCP

WHAT IT DOES

What taskwarrior_start does on Taskwarrior MCP Server

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

Starting a task in Taskwarrior typically transitions its state and may trigger side effects like updating timestamps or triggering dependent tasks. This is an action that modifies system state beyond simple data retrieval, making it Execute rather than Write (which would be reversible schema changes). It's not Destructive because starting a task is reversible.

From the tool's definition Tool name 'taskwarrior_start' on a task management server; sibling tools include taskwarrior_complete, taskwarrior_delete, and taskwarrior_modify, indicating this tool likely triggers a state change (marking a task as started/in progress).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taskwarrior_start Rate-limited

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

FAQ

Questions about taskwarrior_start

What does the taskwarrior_start tool do? +

taskwarrior_start. It is categorised as a Execute tool in the Taskwarrior 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 taskwarrior_start? +

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

What risk level is taskwarrior_start? +

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

Can I rate-limit taskwarrior_start? +

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

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

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