Close a communication room (soft delete - marks as closed but keeps data)
AI agents use close_room to create or update resources in ZMCPTools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZMCPTools environment.
This tool modifies the state of a communication room by marking it closed, which is a write operation that changes data but remains reversible (the room and its data are retained, just marked as closed). This is less severe than destructive operations that permanently delete data, but more severe than read-only queries.
From the tool's definition 'soft delete - marks as closed but keeps data' indicates a reversible state change (marking a room as closed rather than permanently destroying it)
Documented attack patterns abuse exactly the kind of access close_room gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for close_room:
{
"version": "1",
"default": "deny",
"tools": {
"close_room": {
"limits": [
{
"counter": "close_room_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_room 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.
Free to start. No card required.
Close a communication room (soft delete - marks as closed but keeps data). It is categorised as a Write tool in the ZMCPTools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for close_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 ZMCPTools. Nothing to install.
close_room 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 close_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 close_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.
close_room is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.