snow_widget_test · Serac MCP: Risk & Policy

WHAT IT DOES

What snow_widget_test does on Serac

AI agents invoke snow_widget_test to trigger actions in Serac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why snow_widget_test needs a policy

The tool actively executes code (client/server scripts, API calls) within a ServiceNow environment across multiple test scenarios. Running scripts and making API calls constitutes execution with potentially broad side effects depending on what those scripts do. The blast radius is high because misconfigured or malicious test scenarios could trigger unintended operations across ServiceNow services.

From the tool's definition Executes comprehensive widget testing with multiple data scenarios. Validates client/server scripts, API calls, dependencies, and generates coverage reports.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_widget_test Rate-limited

snow_widget_test stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_widget_test": {
      "limits": [
        {
          "counter": "snow_widget_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Serac, so you can run agents against it safely.

FAQ

Questions about snow_widget_test

What does the snow_widget_test tool do? +

Executes comprehensive widget testing with multiple data scenarios. Validates client/server scripts, API calls, dependencies, and generates coverage reports. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on snow_widget_test? +

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

snow_widget_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit snow_widget_test? +

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

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

snow_widget_test 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.