list_discovered_devices

List per-device Discovery results (discovery_device_history) — classification, resulting CI, and issue count. Use to answer

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/list-discovered-devices.md

WHAT IT DOES

What list_discovered_devices does on ServiceNow-MCP

AI agents call list_discovered_devices 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.

RISK

Why list_discovered_devices is rated Low

This tool retrieves and lists discovery data with no side effects. The verb 'list' and the action of querying historical discovery results are characteristic of Read operations. The blast radius of misuse is minimal—an agent could retrieve sensitive infrastructure information but cannot modify, delete, or execute operations.

From the tool's definition Tool name 'list_discovered_devices' and description 'List per-device Discovery results' indicate a retrieval operation that queries discovery_device_history records to return classification, resulting CI, and issue count without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_discovered_devices 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 list_discovered_devices, this is the rule to start with:

list_discovered_devices Allowed

list_discovered_devices is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_discovered_devices": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every list_discovered_devices call is checked against it from then on.

FAQ

Questions about list_discovered_devices

What does the list_discovered_devices tool do? +

List per-device Discovery results (discovery_device_history) — classification, resulting CI, and issue count. Use to answer. 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 list_discovered_devices? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for list_discovered_devices: 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 list_discovered_devices? +

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

Can I rate-limit list_discovered_devices? +

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

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

list_discovered_devices 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.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →