This record as markdown: /tools/nasbridge/snapshot-create.md
What snapshot_create does on Nasbridge
AI agents use snapshot_create 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.
Why snapshot_create is rated Medium
Creating a ZFS snapshot is a Write operation: it adds a new read-only point-in-time copy of a dataset. It does not delete data, execute code, or involve financial transactions. Misuse could consume disk space or create unexpected retention points, giving it medium severity.
From the tool's definition 'Create a ZFS snapshot' — creates a new snapshot object; snapshots are point-in-time copies but do not delete or overwrite existing data
Attacks that exploit this kind of access
The rule that runs snapshot_create 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_create, this is the rule to start with:
snapshot_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every snapshot_create call is checked against it from then on.
Questions about snapshot_create
Create a ZFS snapshot. 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.
Register the Nasbridge MCP server in PolicyLayer and add a rule for snapshot_create: 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.
snapshot_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snapshot_create 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.
Set action: deny in the PolicyLayer policy for snapshot_create. 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.
snapshot_create 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.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue