Update an existing project
AI agents use update_project_by_projectID 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.
This tool modifies project data reversibly. While it affects multiple dependent tasks and potentially team collaboration, it does not delete data irreversibly, execute arbitrary code, move money, or trigger external operations.
From the tool's definition Tool name 'update_project_by_projectID' and description 'Update an existing project' indicate modification of existing data. The operation is reversible (subsequent updates can revert changes), distinguishing it from destructive operations.
Documented attack patterns abuse exactly the kind of access update_project_by_projectID 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 update_project_by_projectID:
{
"version": "1",
"default": "deny",
"tools": {
"update_project_by_projectID": {
"limits": [
{
"counter": "update_project_by_projectid_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_project_by_projectID 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.
Update an existing project. 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 update_project_by_projectID: 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.
update_project_by_projectID 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 update_project_by_projectID 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 update_project_by_projectID. 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.
update_project_by_projectID 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.