Delete a sub API key.
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.
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
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.
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.
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.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →