crow_room_close
Close an active companion room. Invalidates the room token and optionally notifies participants.
This record as markdown: /tools/kh0pper-crow/crow-room-close.md
What crow_room_close does on Crow
AI agents use crow_room_close to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why crow_room_close is rated Medium
This tool modifies data (room state, token validity) and affects an active system, but does not permanently delete underlying data or resources. Closing a room is reversible through reopening/recreation. The blast radius is moderate—it disrupts current participants but doesn't cause permanent data loss or financial harm.
From the tool's definition Tool description: 'Close an active companion room. Invalidates the room token and optionally notifies participants.' - the action of closing a room and invalidating its token modifies the state of an active collaboration session.
Attacks that exploit this kind of access
The rule that runs crow_room_close 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 crow_room_close, this is the rule to start with:
crow_room_close stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_room_close call is checked against it from then on.
Questions about crow_room_close
Close an active companion room. Invalidates the room token and optionally notifies participants. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_room_close: 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.
crow_room_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crow_room_close 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 crow_room_close. 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.
crow_room_close 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.
This server
Across the catalogue