Critical Risk →

delete-inbox-notification

Delete a Liveblocks inbox notification

How to control delete-inbox-notification ↓

What delete-inbox-notification does on Liveblocks

AI agents call delete-inbox-notification 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.

Critical Risk

Why delete-inbox-notification needs a policy

This tool permanently removes an inbox notification, which cannot be undone. While the blast radius is limited to a single notification record (rather than bulk data), the destructive nature of deletion places it in the Destructive category rather than Write.

From the tool's definition Tool is explicitly named 'delete-inbox-notification' with description 'Delete a Liveblocks inbox notification'. The verb 'delete' combined with the action of removing a notification record represents an irreversible deletion operation.

Documented attack patterns abuse exactly the kind of access delete-inbox-notification gives an agent:

How to control delete-inbox-notification

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-inbox-notification:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-inbox-notification"
  ]
}

delete-inbox-notification disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Liveblocks — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-inbox-notification

What does the delete-inbox-notification tool do? +

Delete a Liveblocks inbox notification. 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.

How do I enforce a policy on delete-inbox-notification? +

Register the Liveblocks MCP server in PolicyLayer and add a rule for delete-inbox-notification: 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.

What risk level is delete-inbox-notification? +

delete-inbox-notification is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-inbox-notification? +

Yes. Add a rate_limit block to the delete-inbox-notification 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.

How do I block delete-inbox-notification completely? +

Set action: deny in the PolicyLayer policy for delete-inbox-notification. 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.

What MCP server provides delete-inbox-notification? +

delete-inbox-notification 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.

Enforce policy on every Liveblocks tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.