snow_create_notification · Serac MCP: Risk & Policy

WHAT IT DOES

What snow_create_notification does on Serac

AI agents use snow_create_notification 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 IT NEEDS A POLICY

Why snow_create_notification needs a policy

This tool creates a new notification configuration in ServiceNow, which is a write operation that persists data to the notification system. While it doesn't delete or execute arbitrary code, it does irreversibly create a new notification rule that can affect email delivery workflows.

From the tool's definition Creates or configures an event-driven email notification (sysevent_email_action) in ServiceNow with recipients, subject, and message template settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_create_notification Rate-limited

snow_create_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_create_notification": {
      "limits": [
        {
          "counter": "snow_create_notification_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Serac, so you can run agents against it safely.

FAQ

Questions about snow_create_notification

What does the snow_create_notification tool do? +

Configure an event-driven email notification (sysevent_email_action): fires when records on a table match a condition, with recipients, subject, inline message, or a sysevent_email_template (resolved by sys_id or template name). 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.

How do I enforce a policy on snow_create_notification? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_create_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 Serac. Nothing to install.

What risk level is snow_create_notification? +

snow_create_notification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_create_notification? +

Yes. Add a rate_limit block to the snow_create_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 snow_create_notification completely? +

Set action: deny in the PolicyLayer policy for snow_create_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 snow_create_notification? +

snow_create_notification 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.

// THE FULL RECORD

snow_create_notification is one line of Serac's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →