snow_sanitize_input

Escape a user-supplied string against html, sql, or script-injection contexts. Note: prefer parameterized queries for SQL — sanitization is a fallback, not the primary defense.

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-sanitize-input.md

WHAT IT DOES

What snow_sanitize_input does on Serac

AI agents call snow_sanitize_input 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_sanitize_input is rated Low

This is a defensive utility that reads/transforms input strings to escape potentially dangerous characters. It does not retrieve data, modify records, execute code, delete anything, or commit financial transactions. The note about preferring parameterized queries confirms this is a secondary defensive measure, not a primary operation.

From the tool's definition Tool name 'snow_sanitize_input' and description 'Escape a user-supplied string against html, sql, or script-injection contexts' indicate a data sanitization utility.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

snow_sanitize_input Allowed

snow_sanitize_input 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_sanitize_input": {}
  }
}

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_sanitize_input call is checked against it from then on.

FAQ

Questions about snow_sanitize_input

What does the snow_sanitize_input tool do? +

Escape a user-supplied string against html, sql, or script-injection contexts. Note: prefer parameterized queries for SQL — sanitization is a fallback, not the primary defense. 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_sanitize_input? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_sanitize_input: 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_sanitize_input? +

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

Can I rate-limit snow_sanitize_input? +

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

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

snow_sanitize_input 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

get_example_input on 0gzk → The MCP Attack Database →

Guides

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