delete_sub_uid

Delete a sub UID.

SERVERBybit SOURCEjohnnywic/bybit-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/delete-sub-uid.md

WHAT IT DOES

What delete_sub_uid does on Bybit

AI agents call delete_sub_uid to permanently remove resources in Bybit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_sub_uid is rated Critical

Deletion of a sub UID is an irreversible action that cannot be undone. It results in permanent loss of an account entity and likely cascading effects on associated permissions, data, and trading activity. This meets the definition of Destructive: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.

From the tool's definition Tool name 'delete_sub_uid' explicitly uses the verb 'delete', and the description states it will 'Delete a sub UID', indicating irreversible removal of a subordinate user account or identity.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_sub_uid safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_sub_uid, this is the rule to start with:

delete_sub_uid Hidden

delete_sub_uid is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_sub_uid"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every delete_sub_uid call is checked against it from then on.

FAQ

Questions about delete_sub_uid

What does the delete_sub_uid tool do? +

Delete a sub UID. It is categorised as a Destructive tool in the Bybit 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_uid? +

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

What risk level is delete_sub_uid? +

delete_sub_uid 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_uid? +

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

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

delete_sub_uid is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bybit, and thousands of servers like it.

This server

All 245 Bybit tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →