update_notification
Update an existing email notification (requires WRITE_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/update-notification.md
What update_notification does on ServiceNow MCP Server
AI agents use update_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 update_notification is rated Medium
This tool modifies email notification configurations in ServiceNow. While reversible (not destructive), it can alter communication settings that affect business processes and notifications. The scope is limited to updating notification settings rather than arbitrary data, placing it at medium severity. The requirement for a write-enable flag suggests it's recognized as a sensitive operation by the system.
From the tool's definition Tool name 'update_notification' and description 'Update an existing email notification' indicate modification of existing data. The requirement flag 'WRITE_ENABLED=true' confirms this is a write operation.
Attacks that exploit this kind of access
The rule that runs update_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 update_notification, this is the rule to start with:
update_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 update_notification call is checked against it from then on.
Questions about update_notification
Update an existing email notification (requires WRITE_ENABLED=true). 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 update_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.
update_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 update_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 update_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.
update_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