get_instance_diagnostics
Get live instance performance diagnostics: JVM memory, semaphore pools (concurrency/queue depth), and cluster node status — the data behind the Performance homepage (/stats.do)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/get-instance-diagnostics.md
What get_instance_diagnostics does on ServiceNow-MCP
AI agents call get_instance_diagnostics 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_instance_diagnostics is rated Low
This tool queries and retrieves monitoring/diagnostic data with no side effects. It provides observability into system state but does not create, modify, delete, or execute operations. The data retrieved is system health information useful for operational awareness but not sensitive user data.
From the tool's definition Tool retrieves live instance performance diagnostics (JVM memory, semaphore pools, cluster node status) from the Performance homepage (/stats.do). Uses 'Get' verb and 'diagnostics' (retrieval action).
Attacks that exploit this kind of access
The rule that runs get_instance_diagnostics 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_instance_diagnostics, this is the rule to start with:
get_instance_diagnostics 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_instance_diagnostics call is checked against it from then on.
Questions about get_instance_diagnostics
Get live instance performance diagnostics: JVM memory, semaphore pools (concurrency/queue depth), and cluster node status — the data behind the Performance homepage (/stats.do). 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_instance_diagnostics: 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_instance_diagnostics 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_diagnostics 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_diagnostics. 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_diagnostics 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