AI agents use update-notification-settings 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 modifies notification settings, which is a reversible write operation. The severity is medium because misconfiguration could cause notification spam or silence important alerts, but the impact is limited to the user's preferences without affecting core data or financial systems.
From the tool's definition Tool name 'update-notification-settings' and description 'Update Liveblocks notification settings' indicate modification of user configuration data (notification preferences).
Documented attack patterns abuse exactly the kind of access update-notification-settings 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 update-notification-settings:
{
"version": "1",
"default": "deny",
"tools": {
"update-notification-settings": {
"limits": [
{
"counter": "update-notification-settings_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-notification-settings 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.
Update Liveblocks notification settings. 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 update-notification-settings: 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.
update-notification-settings 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 update-notification-settings 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 update-notification-settings. 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.
update-notification-settings 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.