taskwarrior_project_summary
AI agents call taskwarrior_project_summary 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.
Based on the tool name, it likely retrieves and displays a summary of Taskwarrior projects, which is a read operation. The sibling tools include list, get, and bulk_get operations, suggesting this fits a read pattern. However, the empty description lowers confidence. No evidence of write, execute, or destructive behavior.
From the tool's definition Tool name 'taskwarrior_project_summary' suggests retrieving a summary of projects; description is empty and uninformative.
Attacks that exploit this kind of access
taskwarrior_project_summary. 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_project_summary: 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_project_summary 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_project_summary 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_project_summary. 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_project_summary 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 →