Retrieves and displays all tasks from a specified project. If no project is provided, tasks from the default Inbox project will be shown. The response includes task details such as ID, title, content, due date, priority, tags, and completion status.
AI agents call list-tasks to retrieve information from Dida without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure retrieval operation that queries and displays existing task data without any side effects. It performs a search/list operation typical of Read category tools. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes task information the user already owns or has access to.
From the tool's definition Tool name is 'list-tasks' and description states it 'Retrieves and displays all tasks from a specified project' with no modification or deletion capabilities mentioned.
Documented attack patterns abuse exactly the kind of access list-tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dida, and nothing reaches the server without passing your rules. This is the rule we recommend for list-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"list-tasks": {}
}
}list-tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves and displays all tasks from a specified project. If no project is provided, tasks from the default Inbox project will be shown. The response includes task details such as ID, title, content, due date, priority, tags, and completion status. It is categorised as a Read tool in the Dida MCP Server, which means it retrieves data without modifying state.
Register the Dida 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 Dida. 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 Dida MCP server (zhongwencool/dida-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dida, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Dida tools catalogued and risk-classified — across an index of 43,000+ MCP servers.