list_mid_server_issues

List MID Server issues (ecc_agent_issue) — detected problems with source, occurrence count, and last-detected time

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-mid-server-issues.md

WHAT IT DOES

What list_mid_server_issues does on ServiceNow-MCP

AI agents call list_mid_server_issues 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_mid_server_issues is rated Low

This tool reads diagnostic/monitoring data from ServiceNow's MID Server issue table. It performs a passive query operation with no side effects, aligning with the Read category. Severity is low because it only exposes diagnostic information without access to sensitive credentials or ability to affect system operations. The tool is used for visibility into MID Server health status.

From the tool's definition 'List MID Server issues' retrieves and queries detected problems with metadata (source, occurrence count, last-detected time). No modification, deletion, or execution of external commands implied.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_mid_server_issues Allowed

list_mid_server_issues 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_mid_server_issues": {}
  }
}

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_mid_server_issues call is checked against it from then on.

FAQ

Questions about list_mid_server_issues

What does the list_mid_server_issues tool do? +

List MID Server issues (ecc_agent_issue) — detected problems with source, occurrence count, and last-detected time. 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_mid_server_issues? +

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

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

Can I rate-limit list_mid_server_issues? +

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

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

list_mid_server_issues 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 →