directory_services_leave
Leave the current Active Directory or LDAP domain. This is a DESTRUCTIVE operation —
This record as markdown: /tools/spranab-truenas-mcp/directory-services-leave.md
What directory_services_leave does on Truenas
AI agents call directory_services_leave 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 directory_services_leave is rated Critical
Leaving an Active Directory or LDAP domain is explicitly flagged as destructive by the tool's own description. This action severs the system's domain membership, which cannot be trivially undone — rejoining requires reconfiguration, credential re-entry, and potential loss of domain-bound permissions, group policies, and user access.
From the tool's definition 'Leave the current Active Directory or LDAP domain. This is a DESTRUCTIVE operation'
Attacks that exploit this kind of access
The rule that runs directory_services_leave 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 directory_services_leave, this is the rule to start with:
directory_services_leave 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 directory_services_leave call is checked against it from then on.
Questions about directory_services_leave
Leave the current Active Directory or LDAP domain. This is a DESTRUCTIVE operation —. 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 directory_services_leave: 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.
directory_services_leave 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 directory_services_leave 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 directory_services_leave. 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.
directory_services_leave 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