Archive a project.
AI agents use ticktick_archive_project to create or update resources in TickTick MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TickTick MCP Server environment.
Archiving a project modifies its status/visibility but does not permanently destroy data, making it a Write operation rather than Destructive. The severity is medium because archiving could hide important work context from a user, but the operation is reversible and does not result in data loss or financial impact. Confidence is high based on clear naming and standard archival semantics.
From the tool's definition Tool name 'ticktick_archive_project' and description 'Archive a project' indicates the tool modifies project state by archiving it. Archiving is a reversible operation (projects can be unarchived), distinguishing it from deletion.
Attacks that exploit this kind of access
Archive a project. It is categorised as a Write tool in the TickTick MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_archive_project: 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 MCP Server. Nothing to install.
ticktick_archive_project 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_archive_project 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_archive_project. 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_archive_project is provided by the TickTick MCP Server MCP server (mostafasuliman/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 →