table_query · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What table_query does on ServiceNow MCP Server

AI agents invoke table_query to trigger actions in ServiceNow MCP Server. 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.

WHY IT NEEDS A POLICY

Why table_query needs a policy

While a query operation is typically Read, the ability to query ANY ServiceNow table (including sensitive ones like user credentials, security policies, financial data, HR records) with no described restrictions makes this an Execute-level risk. An AI agent could extract highly sensitive data across the entire ServiceNow instance. The generic, unconstrained nature elevates this beyond a simple Read tool.

From the tool's definition 'Generic table query - query any ServiceNow table' — the tool can query ANY table, implying arbitrary table access including sensitive tables; 'Generic' suggests broad, unconstrained execution scope

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

table_query Rate-limited

table_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": {
    "table_query": {
      "limits": [
        {
          "counter": "table_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow MCP Server, so you can run agents against it safely.

FAQ

Questions about table_query

What does the table_query tool do? +

Generic table query - query any ServiceNow table. It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on table_query? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for table_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 Server. Nothing to install.

What risk level is table_query? +

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

Can I rate-limit table_query? +

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

Set action: deny in the PolicyLayer policy for table_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 table_query? +

table_query is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.