deleteEntityTypePermissionWithId
Hard deletes a permission. This is a dangerous operation and should not be used in most circumstances. This permanently removes the given permission from all grants that had it.
This record as markdown: /tools/io-fusionauth-mcp-api/deleteentitytypepermissionwithid.md
What deleteEntityTypePermissionWithId does on Fusionauth
AI agents call deleteEntityTypePermissionWithId 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 deleteEntityTypePermissionWithId is rated Critical
This tool performs an irreversible deletion that cascades across the system (removes permission from all grants). Hard deletes with system-wide effects on critical access control data represent the highest destructive risk. The description itself warns of the danger and permanent nature of this operation.
From the tool's definition Tool description explicitly states "Hard deletes a permission" and "This is a dangerous operation" that "permanently removes the given permission from all grants that had it." The operation is irreversible and affects multiple entities system-wide.
Attacks that exploit this kind of access
The rule that runs deleteEntityTypePermissionWithId 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 deleteEntityTypePermissionWithId, this is the rule to start with:
deleteEntityTypePermissionWithId 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 deleteEntityTypePermissionWithId call is checked against it from then on.
Questions about deleteEntityTypePermissionWithId
Hard deletes a permission. This is a dangerous operation and should not be used in most circumstances. This permanently removes the given permission from all grants that had it. 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 deleteEntityTypePermissionWithId: 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.
deleteEntityTypePermissionWithId 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 deleteEntityTypePermissionWithId 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 deleteEntityTypePermissionWithId. 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.
deleteEntityTypePermissionWithId 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