run_discovery_scan

[Write] Trigger a ServiceNow Discovery scan for network/infrastructure

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp
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/servicenow-mcp-server/run-discovery-scan.md

What run_discovery_scan does on ServiceNow MCP Server

AI agents invoke run_discovery_scan to trigger actions in ServiceNow MCP Server. 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 run_discovery_scan is rated High

This tool executes a discovery scan against live network infrastructure. While scans are non-destructive, they are Execute-class because they trigger autonomous external operations that perform reconnaissance and may consume resources, generate logs, or trigger alerts. The blast radius is high if an AI agent misconfigures the scan scope or targets critical infrastructure unintentionally.

From the tool's definition Tool name is 'run_discovery_scan' and description states it will 'Trigger a ServiceNow Discovery scan for network/infrastructure'.

Questions about run_discovery_scan

What does the run_discovery_scan tool do? +

[Write] Trigger a ServiceNow Discovery scan for network/infrastructure. It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_discovery_scan? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for run_discovery_scan: 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 Server. Nothing to install.

What risk level is run_discovery_scan? +

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

Can I rate-limit run_discovery_scan? +

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

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

run_discovery_scan is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ServiceNow MCP Server, 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 ServiceNow MCP Server'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.