scan_vulnerabilities

Trigger a vulnerability scan for specified CIs or groups. [Write]

High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/scan-vulnerabilities.md

What scan_vulnerabilities does on NowAIKit — ServiceNow AI Toolkit

AI agents invoke scan_vulnerabilities to trigger actions in NowAIKit — ServiceNow AI Toolkit. 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 scan_vulnerabilities is rated High

Triggering a vulnerability scan is an active execution of an external operation (scanning infrastructure components), not merely writing data. It causes real-world effects (network probing, resource consumption, potential disruption) whose impact depends on the target arguments. Despite the server-provided '[Write]' hint, the action better fits Execute due to the operational side-effects of running a scan.

From the tool's definition "Trigger a vulnerability scan" — actively initiates an external scanning operation against specified CIs or groups

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 NowAIKit — ServiceNow AI Toolkit 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 NowAIKit — ServiceNow AI Toolkit 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 NowAIKit — ServiceNow AI Toolkit. 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 NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of NowAIKit — ServiceNow AI Toolkit's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.