Delete an SMB share by ID. Requires confirm=True.
AI agents call delete_smb_share to permanently remove resources in Truenas Ws — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an SMB share removes a network resource configuration that cannot be automatically recovered without recreation. While the confirm=True requirement adds a minor safeguard, the tool permanently removes access configuration and is irreversible. This qualifies as Destructive rather than Write (which is reversible).
From the tool's definition Tool name is 'delete_smb_share' and description states 'Delete an SMB share by ID.' The verb 'delete' combined with the irreversible nature of removing a share configuration indicates this is a destructive action.
Attacks that exploit this kind of access
Delete an SMB share by ID. Requires confirm=True. It is categorised as a Destructive tool in the Truenas Ws MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Truenas Ws MCP server in PolicyLayer and add a rule for delete_smb_share: 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 Ws. Nothing to install.
delete_smb_share 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 delete_smb_share 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 delete_smb_share. 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.
delete_smb_share is provided by the Truenas Ws MCP server (thoriphes/truenas-ws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →