AI agents use ticktick_update_task to create or update resources in Ticktick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ticktick environment.
This tool modifies task data reversibly—updates can be undone by subsequent updates or by the user. It does not delete data (which would be Destructive) or execute arbitrary code (Execute). The severity is medium because task modification could affect productivity workflows, but the blast radius is limited to the user's task management system without financial or irreversible consequences.
From the tool's definition Server description explicitly states the server enables 'create, update, complete, move, and filter tasks'. The tool name 'ticktick_update_task' directly corresponds to the 'update' capability mentioned.
Attacks that exploit this kind of access
ticktick_update_task. It is categorised as a Write tool in the Ticktick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ticktick MCP server in PolicyLayer and add a rule for ticktick_update_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. Nothing to install.
ticktick_update_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 ticktick_update_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 ticktick_update_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.
ticktick_update_task is provided by the Ticktick MCP server (partymola/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →