AI agents call get_sub_api_keys to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive API key information from a sub-account without altering it. While the Read category applies, the severity is medium rather than low because exposed API keys themselves represent a critical security credential that could enable unauthorized account access if disclosed to malicious agents. However, the tool itself is read-only and performs no destructive or financial actions.
From the tool's definition Tool name 'get_sub_api_keys' and description 'Get all API keys of a sub account' indicate a retrieval operation that queries and returns existing API key data without modification.
Attacks that exploit this kind of access
Get all API keys of a sub account. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_sub_api_keys: 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.
get_sub_api_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_sub_api_keys 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 get_sub_api_keys. 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.
get_sub_api_keys 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.
get_sub_api_keys is one line of Bybit's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →