list_mid_servers
List MID servers and verify they are healthy
This record as markdown: /tools/servicenow-mcp-server/list-mid-servers.md
What list_mid_servers does on ServiceNow MCP Server
AI agents call list_mid_servers 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 list_mid_servers is rated Low
This is a read operation that queries and displays MID (Management, Instrumentation, Deployment) server information and health status. MID servers are critical infrastructure components in ServiceNow that bridge communication between the platform and external systems.
From the tool's definition Tool name is 'list_mid_servers' and description states 'List MID servers and verify they are healthy' — both indicate retrieval and inspection of server status information without modification.
Attacks that exploit this kind of access
The rule that runs list_mid_servers 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 list_mid_servers, this is the rule to start with:
list_mid_servers 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 list_mid_servers call is checked against it from then on.
Questions about list_mid_servers
List MID servers and verify they are healthy. 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 list_mid_servers: 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.
list_mid_servers 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 list_mid_servers 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 list_mid_servers. 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.
list_mid_servers 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