scan_vulnerabilities · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What scan_vulnerabilities does on ServiceNow-MCP

AI agents invoke scan_vulnerabilities to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why scan_vulnerabilities needs a policy

Triggering a vulnerability scan is not a passive read or a simple data write; it actively executes a scanning process that probes systems, consumes resources, and can affect target CI availability or security posture. This places it in Execute rather than Write. Severity is high because misconfigured or unauthorized scans can disrupt systems and expose sensitive information about infrastructure weaknesses.

From the tool's definition 'Trigger a vulnerability scan' — the tool initiates an active external/internal scanning operation against CIs or groups, which is an execution of a process with side effects beyond a simple data write.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_vulnerabilities Rate-limited

scan_vulnerabilities stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_vulnerabilities": {
      "limits": [
        {
          "counter": "scan_vulnerabilities_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 scan_vulnerabilities

What does the scan_vulnerabilities tool do? +

Trigger a vulnerability scan for specified CIs or groups. [Write]. It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_vulnerabilities? +

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

scan_vulnerabilities is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scan_vulnerabilities? +

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

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

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