create_vulnerability_group · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What create_vulnerability_group does on ServiceNow-MCP

AI agents use create_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 create_vulnerability_group needs a policy

This tool creates new vulnerability remediation tasks in ServiceNow, which modifies the CMDB and security posture tracking data. While reversible (tasks can be deleted), creation of vulnerability records affects security operations and has moderate blast radius if misused (e.g., spamming false vulnerability tasks, cluttering remediation workflows, or creating misleading security records).

From the tool's definition Tool name 'create_vulnerability_group' and description 'Create a Vulnerability Group / Remediation Task' indicate the tool creates new records in the sn_vul_vulnerability table.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_vulnerability_group Rate-limited

create_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": {
    "create_vulnerability_group": {
      "limits": [
        {
          "counter": "create_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 create_vulnerability_group

What does the create_vulnerability_group tool do? +

Create a Vulnerability Group / Remediation Task (sn_vul_vulnerability). Being task-based it. 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 create_vulnerability_group? +

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

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

Can I rate-limit create_vulnerability_group? +

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

Set action: deny in the PolicyLayer policy for create_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 create_vulnerability_group? +

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