snow_fuzzy_search

Perform fuzzy search across tables with relevance scoring. Returns sys_id + name + relevance_score for each match. Uses LIKE/CONTAINS queries and ranks by similarity.

SERVERSerac SOURCEserac-labs/serac

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/serac/snow-fuzzy-search.md

WHAT IT DOES

What snow_fuzzy_search does on Serac

AI agents call snow_fuzzy_search to retrieve information from Serac without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why snow_fuzzy_search is rated Low

This tool retrieves search results with relevance scoring from ServiceNow tables. There are no side effects, no data modification, no command execution, and no destructive operations. It is purely a query/retrieval mechanism, fitting squarely in the Read category with low risk since search operations have minimal blast radius even if misused by an AI agent.

From the tool's definition Tool performs 'fuzzy search across tables' and 'Returns sys_id + name + relevance_score' — it retrieves and queries data without modifying, creating, deleting, or executing operations. Uses 'LIKE/CONTAINS queries' which are read-only database operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snow_fuzzy_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_fuzzy_search, this is the rule to start with:

snow_fuzzy_search Allowed

snow_fuzzy_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_fuzzy_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about snow_fuzzy_search

What does the snow_fuzzy_search tool do? +

Perform fuzzy search across tables with relevance scoring. Returns sys_id + name + relevance_score for each match. Uses LIKE/CONTAINS queries and ranks by similarity. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on snow_fuzzy_search? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_fuzzy_search: 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 Serac. Nothing to install.

What risk level is snow_fuzzy_search? +

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

Can I rate-limit snow_fuzzy_search? +

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

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

snow_fuzzy_search is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Serac, and thousands of servers like it.

This server

All 432 Serac tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →