nlq_query
Ask a natural language question and get structured ServiceNow data (ServiceNow NLQ API)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/nlq-query.md
What nlq_query does on ServiceNow-MCP
AI agents call nlq_query 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 nlq_query is rated Low
This tool retrieves data from ServiceNow in response to natural language questions. It is a read-only operation that queries existing data and returns structured results without modifying, executing code, or triggering external operations. The blast radius if misused is limited to unauthorized information disclosure, which is typical of Read category tools.
From the tool's definition Tool description states 'get structured ServiceNow data' with no mention of creating, modifying, or deleting records. The NLQ API is documented as a query interface that retrieves and returns data without side effects.
Attacks that exploit this kind of access
The rule that runs nlq_query 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 nlq_query, this is the rule to start with:
nlq_query 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, apply this rule, and every nlq_query call is checked against it from then on.
Questions about nlq_query
Ask a natural language question and get structured ServiceNow data (ServiceNow NLQ API). 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 nlq_query: 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.
nlq_query 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 nlq_query 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 nlq_query. 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.
nlq_query 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.
This server
Across the catalogue