List tasks for a run with optional filters.
AI agents call list_tasks to retrieve information from Dag Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries task information from a workflow run using optional filters. It performs a read-only operation with no ability to modify state, execute commands, delete data, or commit financial obligations. The blast radius is minimal—incorrect filtering or listing all tasks cannot cause damage beyond information disclosure of already-known tasks within an authorized workflow context.
From the tool's definition Tool name 'list_tasks' and description 'List tasks for a run with optional filters' indicate retrieval/query of task data with no modification or side effects.
Attacks that exploit this kind of access
List tasks for a run with optional filters. It is categorised as a Read tool in the Dag Planner MCP Server, which means it retrieves data without modifying state.
Register the Dag Planner MCP server in PolicyLayer and add a rule for list_tasks: 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 Dag Planner. Nothing to install.
list_tasks 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 list_tasks 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 list_tasks. 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.
list_tasks is provided by the Dag Planner MCP server (shubhamnegi/dag-planner-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 →