New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_discovery_run

Get one Discovery run by sys_id or number (DIS...), including full status fields

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_discovery_run

What does the get_discovery_run tool do? +

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.

How do I enforce a policy on get_discovery_run? +

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.

What risk level is get_discovery_run? +

get_discovery_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_discovery_run? +

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.

How do I block get_discovery_run completely? +

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.

What MCP server provides get_discovery_run? +

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.

// 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'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.