get_api_key_info
Get current API key information (permissions, IP whitelist, etc.).
This record as markdown: /tools/johnnywic-bybit-mcp/get-api-key-info.md
What get_api_key_info does on Bybit
AI agents call get_api_key_info to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_api_key_info is rated Low
While this is a Read operation (no side effects, no state modification), it deserves medium severity because API key information itself is sensitive data. If exposed to an attacker, knowing permissions and IP whitelist settings could enable more targeted attacks or help an attacker understand the scope of compromised credentials.
From the tool's definition The tool is named 'get_api_key_info' and its description states it retrieves 'current API key information (permissions, IP whitelist, etc.)'. This is fundamentally a read/query operation that retrieves data without modifying state.
Attacks that exploit this kind of access
The rule that runs get_api_key_info 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 get_api_key_info, this is the rule to start with:
get_api_key_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every get_api_key_info call is checked against it from then on.
Questions about get_api_key_info
Get current API key information (permissions, IP whitelist, etc.). 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_api_key_info: 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_api_key_info 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_api_key_info 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_api_key_info. 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_api_key_info 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue