Critical Risk →

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.

Part of the Mcp Api MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@fusionauth/mcp-api Destructive

AI agents may call deleteEntityTypePermissionWithId to permanently remove or destroy resources in Mcp Api. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call deleteEntityTypePermissionWithId in a loop, permanently destroying resources in Mcp Api. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-fusionauth-mcp-api.yaml
tools:
  deleteEntityTypePermissionWithId:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Api policy for all 314 tools.

Tool Name deleteEntityTypePermissionWithId
Category Destructive
MCP Server Mcp Api MCP Server
Risk Level Critical

View all 314 tools →

Agents calling destructive-class tools like deleteEntityTypePermissionWithId have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

deleteEntityTypePermissionWithId is one of the critical-risk operations in Mcp Api. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the deleteEntityTypePermissionWithId tool do? +

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 Mcp Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deleteEntityTypePermissionWithId? +

Add a rule in your Intercept YAML policy under the tools section for deleteEntityTypePermissionWithId. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Api MCP server.

What risk level is deleteEntityTypePermissionWithId? +

deleteEntityTypePermissionWithId is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deleteEntityTypePermissionWithId? +

Yes. Add a rate_limit block to the deleteEntityTypePermissionWithId rule in your Intercept 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.

How do I block deleteEntityTypePermissionWithId completely? +

Set action: deny in the Intercept 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.

What MCP server provides deleteEntityTypePermissionWithId? +

deleteEntityTypePermissionWithId is provided by the Mcp Api MCP server (@fusionauth/mcp-api). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.