Create a custom Liveblocks inbox notification
AI agents use trigger-inbox-notification 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 creates a new inbox notification for a user, which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. The blast radius is medium since misuse could spam users with unwanted notifications.
From the tool's definition "Create a custom Liveblocks inbox notification"
Documented attack patterns abuse exactly the kind of access trigger-inbox-notification 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 trigger-inbox-notification:
{
"version": "1",
"default": "deny",
"tools": {
"trigger-inbox-notification": {
"limits": [
{
"counter": "trigger-inbox-notification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}trigger-inbox-notification 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.
Create a custom Liveblocks inbox notification. 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 trigger-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.
trigger-inbox-notification 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 trigger-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.
Set action: deny in the PolicyLayer policy for trigger-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.
trigger-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.
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.