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

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)

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

Questions about get_instance_diagnostics

What does the get_instance_diagnostics tool do? +

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.

How do I enforce a policy on get_instance_diagnostics? +

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.

What risk level is get_instance_diagnostics? +

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

Can I rate-limit get_instance_diagnostics? +

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.

How do I block get_instance_diagnostics completely? +

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.

What MCP server provides get_instance_diagnostics? +

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.

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