AI agents call get-room to retrieve information from Liveblocks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves room information from Liveblocks without modifying, deleting, or executing any operations. It is a standard read operation that queries existing data. The blast radius is minimal—misuse would only expose room metadata or contents.
From the tool's definition Tool is named 'get-room' and described as 'Get a Liveblocks room', which is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get-room gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Liveblocks, and nothing reaches the server without passing your rules. This is the rule we recommend for get-room:
{
"version": "1",
"default": "deny",
"tools": {
"get-room": {}
}
}get-room is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a Liveblocks room. It is categorised as a Read tool in the Liveblocks MCP Server, which means it retrieves data without modifying state.
Register the Liveblocks MCP server in PolicyLayer and add a rule for get-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 Liveblocks. Nothing to install.
get-room is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-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 get-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.
get-room is provided by the Liveblocks MCP server (liveblocks/liveblocks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Liveblocks, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Liveblocks tools catalogued and risk-classified — across an index of 43,000+ MCP servers.