Delete the current master API key.
AI agents call delete_master_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.
Deleting a master API key is a permanent, irreversible action that cannot be undone. This matches the Destructive category definition ('irreversibly deletes... actions that cannot be undone'). The severity is critical because loss of the master API key blocks all API access and could lock an account holder out of their own trading operations.
From the tool's definition Tool name explicitly states 'delete' and description says 'Delete the current master API key' — this is an irreversible destruction of authentication credentials.
Attacks that exploit this kind of access
Delete the current master 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_master_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_master_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_master_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_master_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_master_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 →