update_security_incident · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What update_security_incident does on ServiceNow-MCP

AI agents use update_security_incident 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_security_incident needs a policy

This tool modifies incident records in ServiceNow, a critical IT service management platform. While reversible (Write, not Destructive), updating security incidents could alter investigation records, status, assignments, or remediation tracking—affecting incident response workflows and compliance. High severity due to the sensitive nature of security incidents and their role in organizational risk management.

From the tool's definition Tool name 'update_security_incident' and description 'Update a security incident record' indicate modification of existing data. The description explicitly notes '(requires WRITE_ENABLED=true)' confirming write capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_security_incident Rate-limited

update_security_incident 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_security_incident": {
      "limits": [
        {
          "counter": "update_security_incident_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_security_incident

What does the update_security_incident tool do? +

Update a security incident record (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_security_incident? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for update_security_incident: 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_security_incident? +

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

Can I rate-limit update_security_incident? +

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

Set action: deny in the PolicyLayer policy for update_security_incident. 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_security_incident? +

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