AI agents call get-threads 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.
The tool retrieves/queries threads data from Liveblocks with no side effects. It performs a simple read operation without creating, modifying, deleting, or executing any operations. This is a standard data retrieval function with minimal security risk.
From the tool's definition Tool name 'get-threads' and description 'Get recent Liveblocks threads' indicate data retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access get-threads 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-threads:
{
"version": "1",
"default": "deny",
"tools": {
"get-threads": {}
}
}get-threads 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 recent Liveblocks threads. 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-threads: 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-threads 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-threads 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-threads. 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-threads 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.