Mark a task as completed. Requires both task ID and project ID. Updates the task
AI agents use complete_task to create or update resources in TickTick/Dida365 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TickTick/Dida365 MCP Server environment.
Completing a task modifies task data (status/completion flag) but is reversible—a task can be marked incomplete again. This is a state change rather than deletion or destruction. While it affects task management workflow, the impact is localized to a single task's status and can be undone, placing it in the Write category rather than Destructive.
From the tool's definition Tool description states 'Mark a task as completed' and 'Updates the task', indicating reversible modification of task state.
Documented attack patterns abuse exactly the kind of access complete_task 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 complete_task:
{
"version": "1",
"default": "deny",
"tools": {
"complete_task": {
"limits": [
{
"counter": "complete_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}complete_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mark a task as completed. Requires both task ID and project ID. Updates the task. It is categorised as a Write tool in the TickTick/Dida365 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TickTick/Dida365 MCP Server MCP server in PolicyLayer and add a rule for complete_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 TickTick/Dida365 MCP Server. Nothing to install.
complete_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_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 complete_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.
complete_task 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.