update_notification · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What update_notification does on ServiceNow-MCP

AI agents use update_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 update_notification needs a policy

This tool modifies existing notification configurations within ServiceNow. While the change is reversible (not Destructive), it affects email notifications that could impact many users or stakeholders if misconfigured. The high severity reflects the potential for an AI agent to inadvertently alter critical notification settings, disrupt alert delivery, or enable unauthorized communications.

From the tool's definition Tool name is 'update_notification' with description stating 'Update an existing email notification (requires WRITE_ENABLED=true)'. The verb 'Update' and explicit WRITE_ENABLED requirement indicate a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_notification Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_notification": {
      "limits": [
        {
          "counter": "update_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 update_notification

What does the update_notification tool do? +

Update an existing email notification (requires WRITE_ENABLED=true). 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 update_notification? +

Register the ServiceNow- 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. Nothing to install.

What risk level is update_notification? +

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

Can I rate-limit update_notification? +

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.

How do I block update_notification completely? +

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.

What MCP server provides update_notification? +

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