snow_clone_instance_artifact · Serac MCP: Risk & Policy

WHAT IT DOES

What snow_clone_instance_artifact does on Serac

AI agents use snow_clone_instance_artifact 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.

WHY IT NEEDS A POLICY

Why snow_clone_instance_artifact needs a policy

This tool performs data replication and migration across ServiceNow instances, creating artifacts in target environments. Although cloning is technically reversible (artifacts could be deleted), it modifies system state across multiple instances and could corrupt production if misused.

From the tool's definition The tool description states it 'Clones artifacts directly between ServiceNow instances (dev→test→prod)'. This involves copying/replicating data and configurations across environments, which modifies the target instance state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_clone_instance_artifact Rate-limited

snow_clone_instance_artifact 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_clone_instance_artifact": {
      "limits": [
        {
          "counter": "snow_clone_instance_artifact_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_clone_instance_artifact

What does the snow_clone_instance_artifact tool do? +

Clones artifacts directly between ServiceNow instances (dev→test→prod). Handles authentication, dependency resolution, and data migration. 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_clone_instance_artifact? +

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

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

Can I rate-limit snow_clone_instance_artifact? +

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

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

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