delete-all-inbox-notifications

THE RISK

Critical Risk

Why delete-all-inbox-notifications needs a policy

This tool irreversibly deletes data in bulk (all inbox notifications for a user). The destructive nature (cannot be undone without restoration from backups) and broad scope (all notifications) warrant the Destructive category and high severity. An AI agent misusing this could permanently remove important notification records.

From the tool's definition Tool name contains "delete-all" and description states "Delete all Liveblocks inbox notifications". The 'delete-all' prefix combined with 'Delete' verb indicates irreversible bulk removal of data.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control delete-all-inbox-notifications

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-all-inbox-notifications:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-all-inbox-notifications"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Liveblocks tools

Destructive delete-comment Delete a Liveblocks comment Destructive delete-inbox-notification Delete a Liveblocks inbox notification Destructive delete-notification-settings Delete Liveblocks notification settings Destructive delete-room Delete a Liveblocks room Destructive delete-room-subscription-settings Delete a Liveblocks room Destructive delete-thread Delete a Liveblocks thread Destructive remove-comment-reaction Remove a reaction from a Liveblocks comment Execute broadcast-event Broadcast an event to a Liveblocks room

All 39 Liveblocks tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Liveblocks → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-all-inbox-notifications

What does the delete-all-inbox-notifications tool do? +

Delete all Liveblocks inbox notifications. 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-all-inbox-notifications? +

Register the Liveblocks MCP server in PolicyLayer and add a rule for delete-all-inbox-notifications: 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-all-inbox-notifications? +

delete-all-inbox-notifications 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-all-inbox-notifications? +

Yes. Add a rate_limit block to the delete-all-inbox-notifications 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-all-inbox-notifications completely? +

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

delete-all-inbox-notifications 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.

CHECK YOUR STACK →