snapshot_clone

Clone a snapshot into a new dataset

SERVERNasbridge SOURCEmaverick0628/nasbridge

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/nasbridge/snapshot-clone.md

WHAT IT DOES

What snapshot_clone does on Nasbridge

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

RISK

Why snapshot_clone is rated Medium

Cloning a snapshot creates a new dataset from an existing snapshot. This is a Write operation as it creates new data/resources. It does not delete or overwrite existing data, and is reversible by deleting the cloned dataset. Severity is medium as it consumes storage resources and could be misused to create many large datasets.

From the tool's definition Clone a snapshot into a new dataset

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snapshot_clone safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snapshot_clone, this is the rule to start with:

snapshot_clone Rate-limited

snapshot_clone 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": {
    "snapshot_clone": {
      "limits": [
        {
          "counter": "snapshot_clone_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 Nasbridge, apply this rule, and every snapshot_clone call is checked against it from then on.

FAQ

Questions about snapshot_clone

What does the snapshot_clone tool do? +

Clone a snapshot into a new dataset. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on snapshot_clone? +

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

What risk level is snapshot_clone? +

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

Can I rate-limit snapshot_clone? +

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

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

snapshot_clone is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

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