Low Risk

search_records

search_records

How to control search_records ↓

What search_records does on ServiceNow MCP Server

AI agents call search_records to retrieve information from ServiceNow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_records needs a policy

Search operations retrieve data without modification. Even though the description is empty, the tool name and server context clearly indicate a read-only query function. Low severity because searching records has minimal blast radius—no data is created, deleted, or moved.

From the tool's definition Tool name 'search_records' indicates a search/retrieval operation. Server description confirms agents can 'search for records' as a core read capability.

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

How to control search_records

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

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

search_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 ServiceNow MCP Server — 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 search_records

What does the search_records tool do? +

search_records. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_records? +

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

What risk level is search_records? +

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

Can I rate-limit search_records? +

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

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

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

Enforce policy on every ServiceNow MCP Server tool call.

Start from ServiceNow MCP Server, 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.

10 ServiceNow MCP Server 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.