ticktick_remove_collaborator

THE RISK

Critical Risk

Why ticktick_remove_collaborator needs a policy

Removing a collaborator from a project is an irreversible action (or at least a significant access-control change that cannot be automatically undone) that revokes another user's project access. This falls under Destructive as it permanently removes permissions/membership. Misuse by an AI agent could lock out legitimate collaborators from projects, with high blast radius in a collaborative environment.

From the tool's definition 'Remove project access' — removing a collaborator irreversibly revokes their access to a project

Documented attack patterns abuse exactly the kind of access ticktick_remove_collaborator gives an agent:

POLICY

How to control ticktick_remove_collaborator

PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ticktick_remove_collaborator:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "ticktick_remove_collaborator"
  ]
}

ticktick_remove_collaborator disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register TickTick MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More TickTick MCP Server tools

Destructive ticktick_delete_habit Delete a habit permanently Destructive ticktick_delete_tag Delete a tag permanently Destructive ticktick_delete_task Delete a task from TickTick Destructive ticktick_delete_task_attachment Remove attachments Destructive ticktick_delete_task_note Remove task note Destructive ticktick_delete_task_template Remove template Destructive ticktick_reset_user_data Reset or manage user data with various options Execute ticktick_start_focus_session Start a focus/Pomodoro session

All 114 TickTick MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in TickTick MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ticktick_remove_collaborator

What does the ticktick_remove_collaborator tool do? +

Remove project access. It is categorised as a Destructive tool in the TickTick MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on ticktick_remove_collaborator? +

Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_remove_collaborator: 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.

What risk level is ticktick_remove_collaborator? +

ticktick_remove_collaborator is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ticktick_remove_collaborator? +

Yes. Add a rate_limit block to the ticktick_remove_collaborator 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.

How do I block ticktick_remove_collaborator completely? +

Set action: deny in the PolicyLayer policy for ticktick_remove_collaborator. 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.

What MCP server provides ticktick_remove_collaborator? +

ticktick_remove_collaborator is provided by the TickTick MCP Server MCP server (liadgez/ticktick-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TickTick MCP Server tool call.

Start from TickTick MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →