Query ServiceNow records with filtering, field selection, pagination, and sorting
AI agents call query_records to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
query_records retrieves ServiceNow records through parameterized queries. It supports filtering and sorting but has no capacity to modify, delete, or execute operations. This is a classic Read operation with minimal blast radius — worst case is unauthorized access to existing data, not system compromise or data loss.
From the tool's definition Tool performs 'Query' operations with 'filtering, field selection, pagination, and sorting' — standard read-only data retrieval patterns with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Query ServiceNow records with filtering, field selection, pagination, and sorting. 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 query_records: 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.
query_records 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 query_records 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 query_records. 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.
query_records 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →