Critical Risk

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...

Accepts freeform code/query input (requestBody.query); High parameter count (26 properties)

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

@fusionauth/mcp-api Destructive Risk 5/5

AI agents may call deleteUserBulk 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 deleteUserBulk 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:
  deleteUserBulk:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Api policy for all 310 tools.

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

View all 310 tools →

What does the deleteUserBulk tool do? +

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.. 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 deleteUserBulk? +

Add a rule in your Intercept YAML policy under the tools section for deleteUserBulk. 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 deleteUserBulk? +

deleteUserBulk 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 deleteUserBulk? +

Yes. Add a rate_limit block to the deleteUserBulk 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 deleteUserBulk completely? +

Set action: deny in the Intercept policy for deleteUserBulk. 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 deleteUserBulk? +

deleteUserBulk 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.

Enforce policies on Mcp Api

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.