update_vulnerability_group · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What update_vulnerability_group does on ServiceNow-MCP

AI agents use update_vulnerability_group 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_vulnerability_group needs a policy

The tool modifies vulnerability management data reversibly (state transitions, assignments, dates can be changed again). It does not delete data (Destructive), execute arbitrary code (Execute), nor move money (Financial). State transitions in vulnerability management could have security implications if misused (e.g., marking critical vulnerabilities as resolved), justifying 'high' severity.

From the tool's definition Tool description states 'Update a Vulnerability Group by sys_id — state transitions, (re)assignment, target date, etc.' This explicitly modifies existing records through state transitions and reassignment operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_vulnerability_group Rate-limited

update_vulnerability_group 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_vulnerability_group": {
      "limits": [
        {
          "counter": "update_vulnerability_group_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_vulnerability_group

What does the update_vulnerability_group tool do? +

Update a Vulnerability Group by sys_id — state transitions, (re)assignment, target date, etc. 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_vulnerability_group? +

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

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

Can I rate-limit update_vulnerability_group? +

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

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

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