snow_notification_preferences
Manage user notification preferences and routing rules
This record as markdown: /tools/serac/snow-notification-preferences.md
What snow_notification_preferences does on Serac
AI agents use snow_notification_preferences to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_notification_preferences is rated Medium
This tool creates or modifies user notification preferences and routing rules without irreversibly destroying data. While it affects user settings in ServiceNow, the changes are reversible (preferences can be updated again).
From the tool's definition Manage user notification preferences and routing rules — describes modifying user configuration settings for notifications, which constitutes reversible data changes.
Attacks that exploit this kind of access
The rule that runs snow_notification_preferences safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_notification_preferences, this is the rule to start with:
snow_notification_preferences 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_notification_preferences call is checked against it from then on.
Questions about snow_notification_preferences
Manage user notification preferences and routing rules. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_notification_preferences: 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 Serac. Nothing to install.
snow_notification_preferences 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 snow_notification_preferences 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 snow_notification_preferences. 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.
snow_notification_preferences is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue