Critical Risk →

delete_sub_account

删除子账号(可通过 restore_sub_account 恢复)。请谨慎使用。

Part of the Wjx server.

delete_sub_account can permanently delete data in Wjx, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WJX →

Free to start. No card required.

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

Without a policy, an AI agent could call delete_sub_account in a loop, permanently destroying resources in Wjx. There is no undo for destructive operations. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_sub_account"
  ]
}

See the full Wjx policy for all 58 tools.

Get this rule live on your own Wjx server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WJX →

View all 58 tools →

These attack patterns abuse exactly the kind of access delete_sub_account gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so delete_sub_account only ever does what you allow.

SECURE WJX →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the delete_sub_account tool do? +

删除子账号(可通过 restore_sub_account 恢复)。请谨慎使用。. It is categorised as a Destructive tool in the Wjx 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 delete_sub_account? +

Register the Wjx MCP server in PolicyLayer and add a rule for delete_sub_account: 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 Wjx. Nothing to install.

What risk level is delete_sub_account? +

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

Yes. Add a rate_limit block to the delete_sub_account 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.

How do I block delete_sub_account completely? +

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

delete_sub_account is provided by the Wjx MCP server (wjx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wjx tool call.

Deterministic rules across all 58 Wjx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.