Remove a participant from a chat room.
AI agents call remove_my_chat_participant to permanently remove resources in Thenvoi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a participant from a chat room is an irreversible action — the participant is expelled and the membership record is deleted. While a new invitation could theoretically be issued, the act of removal itself cannot be undone automatically. This qualifies as Destructive. Severity is medium because it affects collaboration/access but does not destroy data or financial assets.
From the tool's definition Remove a participant from a chat room
Attacks that exploit this kind of access
Remove a participant from a chat room. It is categorised as a Destructive tool in the Thenvoi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Thenvoi MCP Server MCP server in PolicyLayer and add a rule for remove_my_chat_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 Thenvoi MCP Server. Nothing to install.
remove_my_chat_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 remove_my_chat_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 remove_my_chat_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.
remove_my_chat_participant is provided by the Thenvoi MCP Server MCP server (thenvoi/thenvoi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →