workspace_collaborations_participants_remove

Run workspace-collaborations.participants.remove through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Critical RISK CLASS

Category Destructive

Parameters 22 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/workspace-collaborations-participants-remove.md

WHAT IT DOES

What workspace_collaborations_participants_remove does on Appaloft

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

Parameter	Type	Required	Description
`participantId`	string	Yes
`collaborationId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why workspace_collaborations_participants_remove is rated Critical

An AI agent that decides to call workspace_collaborations_participants_remove doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Appaloft is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workspace_collaborations_participants_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workspace_collaborations_participants_remove, this is the rule to start with:

workspace_collaborations_participants_remove Hidden

workspace_collaborations_participants_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every workspace_collaborations_participants_remove call is checked against it from then on.

FAQ

Questions about workspace_collaborations_participants_remove

What does the workspace_collaborations_participants_remove tool do? +

Run workspace-collaborations.participants.remove through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does workspace_collaborations_participants_remove accept? +

workspace_collaborations_participants_remove accepts 2 parameters: participantId, collaborationId. Required: participantId, collaborationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on workspace_collaborations_participants_remove? +

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

What risk level is workspace_collaborations_participants_remove? +

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

Yes. Add a rate_limit block to the workspace_collaborations_participants_remove 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 workspace_collaborations_participants_remove completely? +

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

workspace_collaborations_participants_remove is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 428 Appaloft tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →