query_records

What query_records does on ServiceNow MCP Server

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

Despite being classified as Read, the severity is high because ServiceNow typically contains sensitive enterprise data including user information, incidents, configurations, and business processes. An AI agent with unrestricted query access could extract large volumes of sensitive data depending on role-based access controls and what records are queryable.

From the tool's definition Tool description states: 'Query ServiceNow records with filtering, field selection, pagination, and sorting'. The verb 'Query' combined with read-only parameters (filtering, field selection, pagination, sorting) indicates data retrieval with no modification.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_records": {}
  }
}

Questions about query_records