deleteTenantWithId
Deletes the tenant based on the given request (sent to the API as JSON). This permanently deletes all information, metrics, reports and data associated with the tenant and everything under the tenant (applications, users, etc). OR Deletes the tenant for the given Id asynchronously. This method is...
This record as markdown: /tools/io-fusionauth-mcp-api/deletetenantwithid.md
What deleteTenantWithId does on Fusionauth
AI agents call deleteTenantWithId to permanently remove resources in Fusionauth, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteTenantWithId is rated Critical
The tool irreversibly deletes an entire tenant and all associated data (applications, users, metrics, reports). This is unrecoverable data destruction at organizational scale, making it the most severe category (Destructive). Misuse by an AI agent could result in complete loss of a customer's identity infrastructure and data.
From the tool's definition Deletes the tenant based on the given request... This permanently deletes all information, metrics, reports and data associated with the tenant and everything under the tenant (applications, users, etc)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs deleteTenantWithId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteTenantWithId, this is the rule to start with:
deleteTenantWithId 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 Fusionauth, apply this rule, and every deleteTenantWithId call is checked against it from then on.
Questions about deleteTenantWithId
Deletes the tenant based on the given request (sent to the API as JSON). This permanently deletes all information, metrics, reports and data associated with the tenant and everything under the tenant (applications, users, etc). OR Deletes the tenant for the given Id asynchronously. This method is helpful if you do not want to wait for the delete operation to complete. OR Deletes the tenant based on the given Id on the URL. This permanently deletes all information, metrics, reports and data associated with the tenant and everything under the tenant (applications, users, etc). It is categorised as a Destructive tool in the Fusionauth MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fusionauth MCP server in PolicyLayer and add a rule for deleteTenantWithId: 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 Fusionauth. Nothing to install.
deleteTenantWithId 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 deleteTenantWithId 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 deleteTenantWithId. 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.
deleteTenantWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fusionauth, and thousands of servers like it.
Across the catalogue