delete_sub_api_key

Delete a sub API key.

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-api-key.md

WHAT IT DOES

What delete_sub_api_key does on Bybit

AI agents call delete_sub_api_key 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_api_key is rated Critical

This tool performs an irreversible deletion of authentication credentials (a sub API key). Once deleted, the key cannot be recovered and any dependent integrations or access would be severed. This is a destructive action as defined by the category—it cannot be undone.

From the tool's definition Tool name explicitly states 'delete' combined with 'sub API key'. The description confirms irreversible deletion: 'Delete a sub API key.' API keys are critical security credentials; deletion cannot be undone and would immediately revoke access/permissions…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_sub_api_key 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_api_key, this is the rule to start with:

delete_sub_api_key Hidden

delete_sub_api_key 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_api_key"
  ]
}

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_api_key call is checked against it from then on.

FAQ

Questions about delete_sub_api_key

What does the delete_sub_api_key tool do? +

Delete a sub API key. 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_api_key? +

Register the Bybit MCP server in PolicyLayer and add a rule for delete_sub_api_key: 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_api_key? +

delete_sub_api_key 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_api_key? +

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

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

delete_sub_api_key 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

delete_ssh_key on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →web3_revoke_key on 0xarchive → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →