deleteApplicationWithId
Hard deletes an application. This is a dangerous operation and should not be used in most circumstances. This will delete the application, any registrations for that application, metrics and reports for the application, all the roles for the application, and any other data associated with the app...
This record as markdown: /tools/io-fusionauth-mcp-api/deleteapplicationwithid.md
What deleteApplicationWithId does on Fusionauth
AI agents call deleteApplicationWithId 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 deleteApplicationWithId is rated Critical
This tool irreversibly deletes application data and all associated records (registrations, metrics, reports, roles) with no undo capability. The description explicitly warns it is dangerous and could take significant time. This is a quintessential destructive operation with maximum blast radius—misuse could wipe out entire application deployments and their data.
From the tool's definition "Hard deletes an application" and "This is a dangerous operation" combined with "will delete the application, any registrations for that application, metrics and reports for the application, all the roles for the application, and any other data associated…
Attacks that exploit this kind of access
The rule that runs deleteApplicationWithId 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 deleteApplicationWithId, this is the rule to start with:
deleteApplicationWithId 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 deleteApplicationWithId call is checked against it from then on.
Questions about deleteApplicationWithId
Hard deletes an application. This is a dangerous operation and should not be used in most circumstances. This will delete the application, any registrations for that application, metrics and reports for the application, all the roles for the application, and any other data associated with the application. This operation could take a very long time, depending on the amount of data in your database. OR Deactivates the application with the given Id. 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 deleteApplicationWithId: 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.
deleteApplicationWithId 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 deleteApplicationWithId 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 deleteApplicationWithId. 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.
deleteApplicationWithId 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