taskwarrior_dependencies
AI agents call taskwarrior_dependencies to retrieve information from Taskwarrior MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it retrieves or lists task dependencies, similar to the sibling 'taskwarrior_blocked' tool which reads blocking relationships. With no description available, confidence is low, but the naming convention and context of sibling tools (which cover list, get, bulk_get as read operations) suggests this is a read operation. Severity is low as task dependency data is non-sensitive.
From the tool's definition Tool name 'taskwarrior_dependencies' and empty description; sibling tools include taskwarrior_blocked which suggests dependency-related read operations
Attacks that exploit this kind of access
taskwarrior_dependencies. It is categorised as a Read tool in the Taskwarrior MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Taskwarrior MCP Server MCP server in PolicyLayer and add a rule for taskwarrior_dependencies: 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_dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the taskwarrior_dependencies 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_dependencies. 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_dependencies 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 →