schedule_notification · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What schedule_notification does on ServiceNow-MCP

AI agents use schedule_notification to create or update resources in ServiceNow-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.

WHY IT NEEDS A POLICY

Why schedule_notification needs a policy

This tool creates or modifies data (scheduling a notification) in a reversible manner—notifications can be cancelled or rescheduled. The blast radius is medium: misuse could spam users with unwanted notifications, disrupt communication channels, or cause operational confusion, but data and systems remain intact and the action is undoable.

From the tool's definition Tool name 'schedule_notification' combined with description '[Write] Schedule a notification for future delivery' explicitly indicates creation of a new notification record with future delivery scheduling.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_notification Rate-limited

schedule_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": {
    "schedule_notification": {
      "limits": [
        {
          "counter": "schedule_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 ServiceNow-MCP, so you can run agents against it safely.

FAQ

Questions about schedule_notification

What does the schedule_notification tool do? +

[Write] Schedule a notification for future delivery. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on schedule_notification? +

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

What risk level is schedule_notification? +

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

Can I rate-limit schedule_notification? +

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

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

schedule_notification is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.