schedule_notification
[Write] Schedule a notification for future delivery
This record as markdown: /tools/servicenow-mcp-server/schedule-notification.md
What schedule_notification does on ServiceNow MCP Server
AI agents use schedule_notification to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why schedule_notification is rated Medium
Scheduling a notification is a reversible state change that creates or modifies a record in ServiceNow. It does not execute arbitrary code, delete data, or transfer funds. The medium severity reflects that mass scheduling of notifications could disrupt users or overwhelm systems, but the operation remains undoable (scheduled notifications can be cancelled or modified).
From the tool's definition Tool description explicitly states '[Write] Schedule a notification for future delivery' — this creates a new scheduled notification record in the system, modifying state without deletion or financial impact.
Attacks that exploit this kind of access
The rule that runs schedule_notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_notification, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every schedule_notification call is checked against it from then on.
Questions about schedule_notification
[Write] Schedule a notification for future delivery. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server 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 Server. Nothing to install.
schedule_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 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.
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.
schedule_notification is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue