# deleteUserBulk

Deletes the users with the given Ids, or users matching the provided JSON query or queryString. The order of preference is Ids, query and then queryString, it is recommended to only provide one of the three for the request. This method can be used to deactivate or permanently delete (hard-delete) users based upon the hardDelete boolean in the request body. Using the dryRun parameter you may also request the result of the action without actually deleting or deactivating any users. OR Deactivates the users with the given Ids.

Agent View of the PolicyLayer registry record for `deleteUserBulk`. HTML page: https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserbulk

## Facts

- Tool: `deleteUserBulk`
- Server: Fusionauth (`@fusionauth/mcp-api`) — https://policylayer.com/tools/io-fusionauth-mcp-api.md
- Install: `npx -y @fusionauth/mcp-api`
- Homepage: https://github.com/FusionAuth/fusionauth-mcp-api
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "deleteUserBulk",
    "arguments": {}
  }
}
```

## Why deleteUserBulk is rated Critical

This tool performs irreversible deletion of user records at scale. Even with the dryRun parameter available for testing, the core functionality is permanent data destruction that cannot be undone. The bulk nature and ability to match users via queries amplifies the blast radius. This is the most severe category applicable.

From the tool's own definition: "Tool name 'deleteUserBulk' and description explicitly states 'Deletes the users' and 'permanently delete (hard-delete) users' - these are irreversible operations."

## Use case

AI agents call deleteUserBulk 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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fusionauth:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteUserBulk"
  ]
}
```

## Other tools on Fusionauth (313)

- `deleteAPIKeyWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteapikeywithid.md
- `deleteApplicationRoleWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteapplicationrolewithid.md
- `deleteApplicationWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteapplicationwithid.md
- `deleteConnectorWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteconnectorwithid.md
- `deleteConsentWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteconsentwithid.md
- `deleteEmailTemplateWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteemailtemplatewithid.md
- `deleteEntityGrantWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitygrantwithid.md
- `deleteEntityTypePermissionWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitytypepermissionwithid.md
- `deleteEntityTypeWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitytypewithid.md
- `deleteEntityWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteentitywithid.md
- `deleteFormFieldWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteformfieldwithid.md
- `deleteFormWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteformwithid.md
- `deleteGroupMembersWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletegroupmemberswithid.md
- `deleteGroupWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletegroupwithid.md
- `deleteIdentityProviderWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteidentityproviderwithid.md
- `deleteIPAccessControlListWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteipaccesscontrollistwithid.md
- `deleteJwtRefresh` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletejwtrefresh.md
- `deleteKeyWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletekeywithid.md
- `deleteLambdaWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletelambdawithid.md
- `deleteMessageTemplateWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletemessagetemplatewithid.md
- `deleteMessengerWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletemessengerwithid.md
- `deleteOAuthScopeWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteoauthscopewithid.md
- `deleteTenantWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletetenantwithid.md
- `deleteThemeWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deletethemewithid.md
- `deleteUserActionReasonWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuseractionreasonwithid.md
- `deleteUserActionWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuseractionwithid.md
- `deleteUserLinkWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserlinkwithid.md
- `deleteUserRegistrationWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserregistrationwithid.md
- `deleteUserTwoFactorWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteusertwofactorwithid.md
- `deleteUserWithId` — Destructive — https://policylayer.com/tools/io-fusionauth-mcp-api/deleteuserwithid.md
- …and 283 more: https://policylayer.com/tools/io-fusionauth-mcp-api.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-fusionauth-mcp-api · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-fusionauth-mcp-api