This record as markdown: /tools/nasbridge/iscsi-initiator-delete.md
What iscsi_initiator_delete does on Nasbridge
AI agents call iscsi_initiator_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 iscsi_initiator_delete is rated Critical
Deleting an iSCSI initiator group is an irreversible destructive action that removes storage access configuration. This falls into the Destructive category rather than Write because the operation cannot be simply reverted—it permanently removes the initiator group resource.
From the tool's definition Tool name contains 'delete' and description states 'Delete an iSCSI initiator group' — this operation irreversibly removes a storage initiator configuration without ability to undo.
Attacks that exploit this kind of access
The rule that runs iscsi_initiator_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 iscsi_initiator_delete, this is the rule to start with:
iscsi_initiator_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 iscsi_initiator_delete call is checked against it from then on.
Questions about iscsi_initiator_delete
Delete an iSCSI initiator group. 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 iscsi_initiator_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.
iscsi_initiator_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_initiator_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_initiator_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_initiator_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