talk_remove_participant
Remove a participant from a Talk conversation by their attendee ID (from list_participants).
This record as markdown: /tools/aiquila-nextcloud-mcp-server/talk-remove-participant.md
What talk_remove_participant does on AIquila — Nextcloud MCP Server
AI agents call talk_remove_participant to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | Yes | Conversation token |
attendeeId | number | Yes | Attendee ID of the participant to remove |
Parameters from the server's own tool schema.
Why talk_remove_participant is rated Critical
Removing a participant from a conversation is an irreversible action that revokes their access to the conversation. The participant would need to be re-invited to regain access, making this a destructive operation. Misuse could disrupt communications for targeted users across potentially sensitive conversations.
From the tool's definition Remove a participant from a Talk conversation by their attendee ID
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs talk_remove_participant safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For talk_remove_participant, this is the rule to start with:
talk_remove_participant is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every talk_remove_participant call is checked against it from then on.
Questions about talk_remove_participant
Remove a participant from a Talk conversation by their attendee ID (from list_participants). It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
talk_remove_participant accepts 2 parameters: token, attendeeId. Required: token, attendeeId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for talk_remove_participant: 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 AIquila — Nextcloud MCP Server. Nothing to install.
talk_remove_participant is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the talk_remove_participant 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 talk_remove_participant. 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.
talk_remove_participant is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
Across the catalogue