Critical Risk →

nfs_share_delete

Delete an NFS share/export

How to control nfs_share_delete ↓

What nfs_share_delete does on Truenas

AI agents call nfs_share_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.

Critical Risk

Why nfs_share_delete needs a policy

Deletion of NFS shares is irreversible and can cause immediate loss of access to shared storage resources for all clients depending on that export. This impacts infrastructure availability and data accessibility. While it doesn't directly delete data files, removing the share itself is an unrecoverable action that warrants Destructive classification.

From the tool's definition Tool name is 'nfs_share_delete' and description states 'Delete an NFS share/export'. The verb 'Delete' combined with the irreversible nature of removing network file system shares (a core infrastructure resource) makes this destructive.

Documented attack patterns abuse exactly the kind of access nfs_share_delete gives an agent:

How to control nfs_share_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for nfs_share_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "nfs_share_delete"
  ]
}

nfs_share_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about nfs_share_delete

What does the nfs_share_delete tool do? +

Delete an NFS share/export. 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.

How do I enforce a policy on nfs_share_delete? +

Register the Truenas MCP server in PolicyLayer and add a rule for nfs_share_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.

What risk level is nfs_share_delete? +

nfs_share_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit nfs_share_delete? +

Yes. Add a rate_limit block to the nfs_share_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.

How do I block nfs_share_delete completely? +

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

What MCP server provides nfs_share_delete? +

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

Enforce policy on every Truenas tool call.

Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.