snow_github_deploy

Server Serac serac-labs/serac

Category Execute

Risk class High

Parameters 00 required

WHAT IT DOES

What snow_github_deploy does on Serac

AI agents invoke snow_github_deploy 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_github_deploy needs a policy

This tool triggers external operations (GitHub file deployment to ServiceNow) whose effects are determined by the arguments provided (source_path, source_directory, bulk flag). While it modifies ServiceNow artifacts, the key characteristic is that it executes a deployment process rather than simply creating/updating data directly.

From the tool's definition Tool description states it 'Deploy files directly from GitHub to ServiceNow' with three modes of deployment including 'each file becomes a separate artifact'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_github_deploy Rate-limited

snow_github_deploy 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_github_deploy": {
      "limits": [
        {
          "counter": "snow_github_deploy_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_github_deploy

What does the snow_github_deploy tool do? +

Deploy files directly from GitHub to ServiceNow — content never passes through LLM context. Three modes: 1. Single file: source_path → one artifact field 2. Directory → Widget: source_directory auto-maps files (template.html→template, server.js→script, etc.) 3. Bulk: source_directory + bulk=true → each file becomes a separate artifact Requires: Enterprise license with. 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_github_deploy? +

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

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

Can I rate-limit snow_github_deploy? +

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

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

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