matrix_leave_room
Leave a room. Destructive — your messages stay but you lose access. Rate-limited: 30/hour.
This record as markdown: /tools/kh0pper-crow/matrix-leave-room.md
What matrix_leave_room does on Crow
AI agents call matrix_leave_room to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why matrix_leave_room is rated Critical
Leaving a Matrix room is an irreversible action from the user's perspective: once left, access is lost and rejoining may not be possible (depending on room settings/invite requirements). The description itself flags this as 'Destructive'. Messages remain but the agent permanently loses participation rights, making this a high-severity destructive action.
From the tool's definition 'Leave a room. Destructive — your messages stay but you lose access.' — explicitly labeled destructive and results in irreversible loss of access to the room.
Attacks that exploit this kind of access
The rule that runs matrix_leave_room safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For matrix_leave_room, this is the rule to start with:
matrix_leave_room 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 Crow, apply this rule, and every matrix_leave_room call is checked against it from then on.
Questions about matrix_leave_room
Leave a room. Destructive — your messages stay but you lose access. Rate-limited: 30/hour. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for matrix_leave_room: 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 Crow. Nothing to install.
matrix_leave_room 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 matrix_leave_room 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 matrix_leave_room. 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.
matrix_leave_room is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue