taskwarrior_context · Taskwarrior MCP Server MCP

WHAT IT DOES

What taskwarrior_context does on Taskwarrior MCP Server

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

WHY IT NEEDS A POLICY

Why taskwarrior_context needs a policy

The tool likely modifies Taskwarrior context settings, which is a reversible configuration change. While the empty description prevents high confidence, the naming pattern and context of a task management tool suggest this sets or switches task filtering/organizational contexts—a Write operation. It is not Destructive (reversible), Execute (no external command execution evident), or Read-only (modifies state).

From the tool's definition Tool name 'taskwarrior_context' and sibling tools on the server include write operations (taskwarrior_add, taskwarrior_modify, taskwarrior_annotate).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

taskwarrior_context Rate-limited

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

FAQ

Questions about taskwarrior_context

What does the taskwarrior_context tool do? +

taskwarrior_context. It is categorised as a Write tool in the Taskwarrior MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on taskwarrior_context? +

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

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

Can I rate-limit taskwarrior_context? +

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

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

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