get_discovery_run
Get one Discovery run by sys_id or number (DIS...), including full status fields
This record as markdown: /tools/tedorigawa001-servicenow-mcp/get-discovery-run.md
What get_discovery_run does on ServiceNow-MCP
AI agents call get_discovery_run to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_discovery_run is rated Low
This tool retrieves and queries discovery run data from ServiceNow by identifier (sys_id or number), returning status information. The verb 'Get' and the absence of any side effects, modifications, or state changes makes this a Read operation. The severity is low because disclosure of discovery run metadata poses minimal risk compared to tools that execute code, delete data, or move money.
From the tool's definition Tool name 'get_discovery_run' and description 'Get one Discovery run by sys_id or number' clearly indicates a retrieval operation with no modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
The rule that runs get_discovery_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_discovery_run, this is the rule to start with:
get_discovery_run is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every get_discovery_run call is checked against it from then on.
Questions about get_discovery_run
Get one Discovery run by sys_id or number (DIS...), including full status fields. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP server in PolicyLayer and add a rule for get_discovery_run: 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.
get_discovery_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_discovery_run 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 get_discovery_run. 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.
get_discovery_run 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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue