This record as markdown: /tools/nasbridge/nfs-share-delete.md
What nfs_share_delete does on Nasbridge
AI agents call nfs_share_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 nfs_share_delete is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs nfs_share_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 nfs_share_delete, this is the rule to start with:
nfs_share_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 nfs_share_delete call is checked against it from then on.
Questions about nfs_share_delete
Delete an NFS share/export. 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 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 Nasbridge. Nothing to install.
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.
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.
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.
nfs_share_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