listSubAPIKeysV5

Query all API keys of a sub-account with pagination support. Use master account

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/listsubapikeysv5.md

WHAT IT DOES

What listSubAPIKeysV5 does on Bybit MCP Server

AI agents call listSubAPIKeysV5 to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why listSubAPIKeysV5 is rated Low

While this is fundamentally a Read operation (retrieves data without modification), the high severity reflects that API keys are extremely sensitive credentials. Exposure of sub-account API keys could allow an attacker to compromise multiple trading accounts and execute unauthorized transactions.

From the tool's definition Tool name and description indicate querying/retrieving API keys: 'Query all API keys' with 'pagination support' and 'Use master account' context. This is a read operation that retrieves sensitive authentication credentials.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listSubAPIKeysV5 safely

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

listSubAPIKeysV5 Allowed

listSubAPIKeysV5 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "listSubAPIKeysV5": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about listSubAPIKeysV5

What does the listSubAPIKeysV5 tool do? +

Query all API keys of a sub-account with pagination support. Use master account. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on listSubAPIKeysV5? +

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

What risk level is listSubAPIKeysV5? +

listSubAPIKeysV5 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit listSubAPIKeysV5? +

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

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

listSubAPIKeysV5 is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-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 MCP Server, and thousands of servers like it.

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →