snow_source_control · Serac MCP: Risk & Policy

WHAT IT DOES

What snow_source_control does on Serac

AI agents invoke snow_source_control 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_source_control needs a policy

Source control operations (commit, push, pull, merge) are external operations that affect code repositories. While some sub-operations are read-like (status, diff), the tool as a unified bridge can execute destructive or publishing actions.

From the tool's definition 'Unified tool for the ServiceNow Studio Source Control plugin. Bridges git-style operations against an application' — git-style operations include push, pull, commit, branch, merge, which trigger external VCS operations and can overwrite or publish code to…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_source_control Rate-limited

snow_source_control 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_source_control": {
      "limits": [
        {
          "counter": "snow_source_control_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_source_control

What does the snow_source_control tool do? +

Unified tool for the ServiceNow Studio Source Control plugin. Bridges git-style operations against an application. 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_source_control? +

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

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

Can I rate-limit snow_source_control? +

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

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

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