group_delete
Delete a group. This is a DESTRUCTIVE operation — the
This record as markdown: /tools/spranab-truenas-mcp/group-delete.md
What group_delete does on Truenas
AI agents call group_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 group_delete is rated Critical
This tool deletes groups irreversibly with no undo capability. While not financial in nature, destructive operations that remove system resources (user groups) represent a high-severity risk if an AI agent misuses it without proper authorization or context. The explicit 'DESTRUCTIVE' label in the description removes ambiguity.
From the tool's definition Tool name 'group_delete' combined with explicit description stating 'This is a DESTRUCTIVE operation' confirms irreversible deletion of group data.
Attacks that exploit this kind of access
The rule that runs group_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 group_delete, this is the rule to start with:
group_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 group_delete call is checked against it from then on.
Questions about group_delete
Delete a group. This is a DESTRUCTIVE operation — the. 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 group_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.
group_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 group_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 group_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.
group_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