AI agents use mark-thread-as-resolved to create or update resources in Liveblocks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Liveblocks environment.
This tool changes thread state from unresolved to resolved, which is a reversible modification of data. It does not delete, execute arbitrary operations, or move money. The blast radius is minimal—marking a thread as resolved affects only collaboration metadata and can be undone by marking it as unresolved again.
From the tool's definition Tool name 'mark-thread-as-resolved' and description 'Mark a Liveblocks thread as resolved' indicate a state change operation that modifies a thread's status/metadata without deleting data or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access mark-thread-as-resolved 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 mark-thread-as-resolved:
{
"version": "1",
"default": "deny",
"tools": {
"mark-thread-as-resolved": {
"limits": [
{
"counter": "mark-thread-as-resolved_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mark-thread-as-resolved 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.
Mark a Liveblocks thread as resolved. It is categorised as a Write tool in the Liveblocks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Liveblocks MCP server in PolicyLayer and add a rule for mark-thread-as-resolved: 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.
mark-thread-as-resolved 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 mark-thread-as-resolved 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 mark-thread-as-resolved. 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.
mark-thread-as-resolved 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.