This record as markdown: /tools/nasbridge/snapshot-task-delete.md
What snapshot_task_delete does on Nasbridge
AI agents call snapshot_task_delete to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why snapshot_task_delete is rated Critical
Deleting a periodic snapshot task is irreversible. It not only removes the task configuration but also stops future automated snapshots from being created, which could lead to data loss if the snapshots were serving as the sole backup mechanism. This is a destructive action with high blast radius in a storage management context.
From the tool's definition 'Delete a periodic snapshot task' — permanently removes a scheduled snapshot task
Attacks that exploit this kind of access
The rule that runs snapshot_task_delete 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_task_delete, this is the rule to start with:
snapshot_task_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every snapshot_task_delete call is checked against it from then on.
Questions about snapshot_task_delete
Delete a periodic snapshot task. It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge MCP server in PolicyLayer and add a rule for snapshot_task_delete: 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_task_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the snapshot_task_delete 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_task_delete. 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_task_delete 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.
Across the catalogue