Retrieve a specific task
AI agents call get_task_by_projectId_and_taskId to retrieve information from TickTick/Dida365 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a specific task by project and task IDs. It performs a read-only query operation with no side effects, no data modification, and no execution of external operations. The minimal blast radius of misuse (exposing task details) places it in the Read category with low severity.
From the tool's definition Tool name includes 'get_task' and description states 'Retrieve a specific task', both indicating data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access get_task_by_projectId_and_taskId gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick/Dida365 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task_by_projectId_and_taskId:
{
"version": "1",
"default": "deny",
"tools": {
"get_task_by_projectId_and_taskId": {}
}
}get_task_by_projectId_and_taskId 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.
Retrieve a specific task. It is categorised as a Read tool in the TickTick/Dida365 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TickTick/Dida365 MCP Server MCP server in PolicyLayer and add a rule for get_task_by_projectId_and_taskId: 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 TickTick/Dida365 MCP Server. Nothing to install.
get_task_by_projectId_and_taskId 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_by_projectId_and_taskId 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_by_projectId_and_taskId. 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_by_projectId_and_taskId is provided by the TickTick/Dida365 MCP Server MCP server (zh1754629545/dida365-mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 TickTick/Dida365 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 TickTick/Dida365 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.