send_push_notification
Send a push notification to mobile app users. [Write]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/send-push-notification.md
What send_push_notification does on ServiceNow-MCP
AI agents use send_push_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 send_push_notification is rated Medium
This tool creates new notification messages and sends them to users' mobile devices. While it has side effects (users receive notifications), the action is reversible and does not permanently alter critical data, delete information, execute arbitrary code, or incur financial obligations. It fits the Write category as a communication mechanism that creates data artifacts.
From the tool's definition Tool description explicitly states 'Send a push notification to mobile app users.' The [Write] tag in the description confirms it modifies/creates notification state.
Attacks that exploit this kind of access
The rule that runs send_push_notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_push_notification, this is the rule to start with:
send_push_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, apply this rule, and every send_push_notification call is checked against it from then on.
Questions about send_push_notification
Send a push notification to mobile app users. [Write]. 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.
Register the ServiceNow MCP server in PolicyLayer and add a rule for send_push_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.
send_push_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 send_push_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 send_push_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.
send_push_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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue