AI agents use ticktick_mark_completion_processed 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 state by marking completion as processed, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary commands (would be Execute), nor involve financial transactions.
From the tool's definition Tool name indicates marking completion as 'processed' — a state change operation on task records. Server description explicitly lists 'complete' tasks as a capability, and this tool's name pattern matches that write operation.
Attacks that exploit this kind of access
ticktick_mark_completion_processed. 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_mark_completion_processed: 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_mark_completion_processed 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_mark_completion_processed 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_mark_completion_processed. 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_mark_completion_processed 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 →