Remove members from a messenger channel
AI agents call dooray_leave_channel_members to permanently remove resources in Dooray MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing members from a channel is an irreversible action that expels users from the communication channel. While the members themselves aren't deleted, their access and membership state is removed, which is difficult to undo automatically and constitutes a destructive operation. This has high blast radius as it could remove multiple members from important communication channels.
From the tool's definition Remove members from a messenger channel
Attacks that exploit this kind of access
Remove members from a messenger channel. It is categorised as a Destructive tool in the Dooray MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for dooray_leave_channel_members: 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 Dooray MCP Server. Nothing to install.
dooray_leave_channel_members 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 dooray_leave_channel_members 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 dooray_leave_channel_members. 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.
dooray_leave_channel_members is provided by the Dooray MCP Server MCP server (kwanok/dooray-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 →