This record as markdown: /tools/spranab-truenas-mcp/iscsi-target-delete.md
What iscsi_target_delete does on Truenas
AI agents call iscsi_target_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 iscsi_target_delete is rated Critical
Deleting an iSCSI target is a destructive action that cannot be easily undone. iSCSI targets are block storage volumes accessible over the network; deleting one removes the storage configuration and access path, potentially causing data unavailability or loss for systems relying on that target.
From the tool's definition Tool name is 'iscsi_target_delete' and description states 'Delete an iSCSI target'. The verb 'delete' combined with a storage/networking resource (iSCSI target) indicates irreversible removal of configuration.
Attacks that exploit this kind of access
The rule that runs iscsi_target_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 iscsi_target_delete, this is the rule to start with:
iscsi_target_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 iscsi_target_delete call is checked against it from then on.
Questions about iscsi_target_delete
Delete an iSCSI target. 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 iscsi_target_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.
iscsi_target_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 iscsi_target_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 iscsi_target_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.
iscsi_target_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