run_discovery_scan · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What run_discovery_scan does on ServiceNow-MCP

AI agents invoke run_discovery_scan 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 run_discovery_scan needs a policy

This tool initiates an active network scanning operation, which is an Execute-category action. While labeled [Write], the actual operation runs external discovery processes that probe infrastructure, potentially affecting network performance, triggering security alerts, or revealing sensitive infrastructure details. The effects are not merely data creation but active external command execution.

From the tool's definition Tool description states it 'Trigger[s] a ServiceNow Discovery scan for network/infrastructure' - triggering an external operation (network discovery scan) whose effects depend on scope/target arguments and cannot be reliably predicted or contained by the AI.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_discovery_scan Rate-limited

run_discovery_scan 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": {
    "run_discovery_scan": {
      "limits": [
        {
          "counter": "run_discovery_scan_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 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 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 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. 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 (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.