snow_generate_records

Generate multiple test records

SERVERSerac SOURCEserac-labs/serac

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/serac/snow-generate-records.md

WHAT IT DOES

What snow_generate_records does on Serac

AI agents use snow_generate_records to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.

RISK

Why snow_generate_records is rated Medium

This tool creates new records (Write category), which is reversible through deletion. Severity is medium because bulk record generation could clutter the ServiceNow instance and consume resources, but the impact is limited to test data and can be undone.

From the tool's definition Tool name 'snow_generate_records' with description 'Generate multiple test records' indicates creation of data records in ServiceNow.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

snow_generate_records Rate-limited

snow_generate_records stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_generate_records": {
      "limits": [
        {
          "counter": "snow_generate_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about snow_generate_records

What does the snow_generate_records tool do? +

Generate multiple test records. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on snow_generate_records? +

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

What risk level is snow_generate_records? +

snow_generate_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_generate_records? +

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

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

snow_generate_records 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

generate_commit on MCP Server PR Pilot →generate_video_title on YouTube MCP Server →generate_devtools_report on Percepta MCP Server →generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →