get_instance_scan_findings
List Instance Scan findings (scan_finding) — best-practice violations, optionally by check or suite result
This record as markdown: /tools/servicenow-mcp-server/get-instance-scan-findings.md
What get_instance_scan_findings does on ServiceNow MCP Server
AI agents call get_instance_scan_findings to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_instance_scan_findings is rated Low
Retrieves security scan data without modification; exposure enables intelligence gathering on system vulnerabilities.
From the tool's definition List Instance Scan findings, best-practice violations, optionally filtered
Attacks that exploit this kind of access
The rule that runs get_instance_scan_findings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_instance_scan_findings, this is the rule to start with:
get_instance_scan_findings 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 Server, apply this rule, and every get_instance_scan_findings call is checked against it from then on.
Questions about get_instance_scan_findings
List Instance Scan findings (scan_finding) — best-practice violations, optionally by check or suite result. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for get_instance_scan_findings: 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.
get_instance_scan_findings 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_instance_scan_findings 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_instance_scan_findings. 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_instance_scan_findings 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.
This server
Across the catalogue