clickup_remove_guest_from_task

A destructive tool on the Clickup MCP server.

SERVERClickup SOURCEtrustxai/clickup-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/clickup-mcp/clickup-remove-guest-from-task.md

What clickup_remove_guest_from_task does on Clickup

AI agents call clickup_remove_guest_from_task to permanently remove resources in Clickup, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clickup_remove_guest_from_task is rated Critical

Removing a guest from a task revokes their access, which is a destructive/irreversible operation (the guest loses access and any associated permissions). The sibling tools show a pattern of add/remove operations for guests on folders, lists, and tasks. Since the description is empty, confidence is reduced, but the naming pattern strongly implies access revocation.

From the tool's definition Tool name: clickup_remove_guest_from_task — 'remove' implies irreversible revocation of access; description is empty providing no additional context.

Questions about clickup_remove_guest_from_task

What does the clickup_remove_guest_from_task tool do? +

clickup_remove_guest_from_task is a destructive tool on the Clickup MCP server. It is categorised as a Destructive tool in the Clickup 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 clickup_remove_guest_from_task? +

Register the Clickup MCP server in PolicyLayer and add a rule for clickup_remove_guest_from_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 Clickup. Nothing to install.

What risk level is clickup_remove_guest_from_task? +

clickup_remove_guest_from_task 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 clickup_remove_guest_from_task? +

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

How do I block clickup_remove_guest_from_task completely? +

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

What MCP server provides clickup_remove_guest_from_task? +

clickup_remove_guest_from_task is provided by the Clickup MCP server (trustxai/clickup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Clickup, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Clickup's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.