AI agents call task_list to retrieve information from Willow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about pending tasks without modifying, deleting, or executing any operations. It is a pure inspection/query operation on the task queue state, making it a Read category tool with low severity since it only exposes task metadata and has no blast radius if misused by an agent.
From the tool's definition Tool name 'task_list' combined with description 'List pending tasks in the Kart queue. Use to inspect backlog before submitting new work' indicates a read-only operation that retrieves and queries task queue status with no side effects.
Attacks that exploit this kind of access
List pending tasks in the Kart queue. Use to inspect backlog before submitting new work. It is categorised as a Read tool in the Willow MCP Server, which means it retrieves data without modifying state.
Register the Willow MCP server in PolicyLayer and add a rule for task_list: 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 Willow. Nothing to install.
task_list 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 task_list 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 task_list. 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.
task_list is provided by the Willow MCP server (rudi193-cmd/willow-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 →