smart_query

Resolve a natural-language request into a ServiceNow table + encoded query and (optionally) run it.

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/smart-query.md

WHAT IT DOES

What smart_query does on ServiceNow-MCP

AI agents invoke smart_query to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why smart_query is rated High

This tool translates natural language into ServiceNow queries and can execute them. The 'optionally run it' clause means it can actively execute queries against ServiceNow tables. Since it operates on natural language that gets resolved into arbitrary queries, and ServiceNow supports DML operations, the blast radius is high.

From the tool's definition "Resolve a natural-language request into a ServiceNow table + encoded query and (optionally) run it"

Attacks that exploit this kind of access

RECOMMENDED RULE

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

smart_query Rate-limited

smart_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "smart_query": {
      "limits": [
        {
          "counter": "smart_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every smart_query call is checked against it from then on.

FAQ

Questions about smart_query

What does the smart_query tool do? +

Resolve a natural-language request into a ServiceNow table + encoded query and (optionally) run it. It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on smart_query? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for smart_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.

What risk level is smart_query? +

smart_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit smart_query? +

Yes. Add a rate_limit block to the smart_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.

How do I block smart_query completely? +

Set action: deny in the PolicyLayer policy for smart_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.

What MCP server provides smart_query? +

smart_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.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →