taskwarrior_add
AI agents use taskwarrior_add 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.
This tool creates new tasks in Taskwarrior, which is a reversible write operation. It modifies the task database by adding entries but does not delete, execute arbitrary code, or move money. Severity is medium because an AI agent adding tasks maliciously could clutter the task management system or create misleading workflows, but the damage is recoverable through deletion.
From the tool's definition Tool name 'taskwarrior_add' combined with server description stating it 'allows users to list, create, modify, and organize tasks' indicates this tool creates new task entries.
Attacks that exploit this kind of access
taskwarrior_add. 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.
Register the Taskwarrior MCP Server MCP server in PolicyLayer and add a rule for taskwarrior_add: 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.
taskwarrior_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the taskwarrior_add 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.
Set action: deny in the PolicyLayer policy for taskwarrior_add. 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.
taskwarrior_add 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →