get_discovery_status
AI agents call get_discovery_status to retrieve information from ServiceNow CMDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a read-only query for discovery process status. While the empty description reduces certainty, the verb 'get' combined with the informational nature of 'discovery_status' indicates data retrieval without side effects. This aligns with Read category patterns (get, query, check). No evidence of destructive, financial, or execution capabilities.
From the tool's definition Tool name 'get_discovery_status' indicates a status-checking operation. In ServiceNow CMDB context, discovery status is informational metadata about the discovery process state.
Attacks that exploit this kind of access
get_discovery_status. It is categorised as a Read tool in the ServiceNow CMDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow CMDB MCP Server MCP server in PolicyLayer and add a rule for get_discovery_status: 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 CMDB MCP Server. Nothing to install.
get_discovery_status 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_status 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_status. 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_status is provided by the ServiceNow CMDB MCP Server MCP server (ketiil/mcp-cmdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →