clickup_add_guest_to_task
A write tool on the Clickup MCP server.
This record as markdown: /tools/clickup-mcp/clickup-add-guest-to-task.md
What clickup_add_guest_to_task does on Clickup
AI agents use clickup_add_guest_to_task to create or update resources in Clickup, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clickup environment.
Why clickup_add_guest_to_task is rated Medium
This tool creates or modifies task data by adding a guest user, which is a reversible change (guests can be removed). This qualifies as Write category. Severity is medium because unauthorized guest additions could expose task information to unintended parties, affecting confidentiality and collaboration state, but the action is reversible and bounded to a single task scope.
From the tool's definition Tool name 'clickup_add_guest_to_task' indicates modification of task access permissions by adding a guest. The description is empty, but the name clearly indicates a write operation that modifies task sharing/membership state.
Attacks that exploit this kind of access
The rule that runs clickup_add_guest_to_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Clickup, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clickup_add_guest_to_task, this is the rule to start with:
clickup_add_guest_to_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Clickup, apply this rule, and every clickup_add_guest_to_task call is checked against it from then on.
Questions about clickup_add_guest_to_task
clickup_add_guest_to_task is a write tool on the Clickup MCP server. It is categorised as a Write tool in the Clickup MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clickup MCP server in PolicyLayer and add a rule for clickup_add_guest_to_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.
clickup_add_guest_to_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 clickup_add_guest_to_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 clickup_add_guest_to_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.
clickup_add_guest_to_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.
This server
Across the catalogue