dataset_delete
Delete a dataset (destructive — requires confirm)
This record as markdown: /tools/spranab-truenas-mcp/dataset-delete.md
What dataset_delete does on Truenas
AI agents call dataset_delete to permanently remove resources in Truenas, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why dataset_delete is rated Critical
Dataset deletion is a permanent, irreversible operation that destroys data. This is the most severe category (Destructive > Execute > Write > Read). Even with a confirmation requirement, the tool's function is to irreversibly remove storage datasets, which could result in complete data loss with no recovery option. Critical severity reflects the potential for catastrophic data loss if misused.
From the tool's definition Tool name is 'dataset_delete' and description explicitly states 'Delete a dataset (destructive — requires confirm)'. The word 'destructive' is used directly in the description, and deletion of datasets is irreversible.
Attacks that exploit this kind of access
The rule that runs dataset_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dataset_delete, this is the rule to start with:
dataset_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 Truenas, apply this rule, and every dataset_delete call is checked against it from then on.
Questions about dataset_delete
Delete a dataset (destructive — requires confirm). It is categorised as a Destructive tool in the Truenas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Truenas MCP server in PolicyLayer and add a rule for dataset_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 Truenas. Nothing to install.
dataset_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 dataset_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 dataset_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.
dataset_delete is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
Across the catalogue