Retrieves detailed information about a specific task by its ID. You must provide the project ID containing the task, or it will default to searching in the Inbox. The response includes all task attributes such as title, content, creation time, modification time, due date, priority, tags, completi...
AI agents call get-task 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 straightforward data retrieval operation that queries task details by ID. It has no capability to modify, delete, or execute actions. The blast radius if misused is minimal—an agent could only access task information it has credentials for. This clearly falls under the Read category with low severity.
From the tool's definition Tool name 'get-task' and description explicitly states it 'Retrieves detailed information about a specific task' with no modification, deletion, or side effects. Returns task attributes only.
Documented attack patterns abuse exactly the kind of access get-task 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 get-task:
{
"version": "1",
"default": "deny",
"tools": {
"get-task": {}
}
}get-task 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 detailed information about a specific task by its ID. You must provide the project ID containing the task, or it will default to searching in the Inbox. The response includes all task attributes such as title, content, creation time, modification time, due date, priority, tags, completion status, and any custom fields. 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 get-task: 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.
get-task 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 get-task 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 get-task. 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.
get-task 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.