Low Risk

count_records

Count records on any ServiceNow table, optionally filtered by an encoded query.

How to control count_records ↓

What count_records does on Now Sdk Ext

AI agents call count_records to retrieve information from Now Sdk Ext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why count_records needs a policy

This tool retrieves aggregate information (record count) from ServiceNow tables without creating, modifying, or deleting data. It has no side effects and presents minimal risk even if misused—an agent could only enumerate table sizes, not access sensitive data contents or modify state.

From the tool's definition Tool name 'count_records' and description 'Count records on any ServiceNow table' indicate data retrieval with no modification. The phrase 'optionally filtered by an encoded query' confirms this is a query operation for counting existing records.

Documented attack patterns abuse exactly the kind of access count_records gives an agent:

How to control count_records

PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for count_records:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "count_records": {}
  }
}

count_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Now Sdk Ext — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about count_records

What does the count_records tool do? +

Count records on any ServiceNow table, optionally filtered by an encoded query. It is categorised as a Read tool in the Now Sdk Ext MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on count_records? +

Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for count_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 Now Sdk Ext. Nothing to install.

What risk level is count_records? +

count_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit count_records? +

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

How do I block count_records completely? +

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

What MCP server provides count_records? +

count_records is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Now Sdk Ext tool call.

Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.