AI agents call delete-comment to permanently remove resources in Liveblocks — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes comment data, which cannot be undone. Deletion is irreversible data destruction. While the blast radius is limited to individual comments (not system-wide), the destructive nature and potential to erase conversation history or evidence makes this high severity. Confidence is high given explicit 'delete' language in both name and description.
From the tool's definition Tool name is 'delete-comment' and description states 'Delete a Liveblocks comment'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete-comment 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 delete-comment:
{
"version": "1",
"default": "deny",
"hide": [
"delete-comment"
]
} delete-comment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a Liveblocks comment. It is categorised as a Destructive tool in the Liveblocks MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Liveblocks MCP server in PolicyLayer and add a rule for delete-comment: 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.
delete-comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-comment 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 delete-comment. 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.
delete-comment 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.