scan_vulnerabilities
Trigger a vulnerability scan for specified CIs or groups. [Write]
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
Attacks that exploit this kind of access
The rule that runs scan_vulnerabilities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NowAIKit — ServiceNow AI Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_vulnerabilities, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect NowAIKit — ServiceNow AI Toolkit, apply this rule, and every scan_vulnerabilities call is checked against it from then on.
Questions about scan_vulnerabilities
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.
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.
scan_vulnerabilities is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Across the catalogue