Query comprehensive information about an API key. Use master or sub-account
AI agents call queryAPIKey to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool falls clearly into the Read category as it performs data retrieval without side effects. While API key information could be considered sensitive from a confidentiality perspective, the tool itself does not create, modify, execute, delete, or move money.
From the tool's definition queryAPIKey retrieves or queries information about an API key without modifying or executing any operations. The verb 'query' and 'retrieve information' indicate a read-only operation.
Documented attack patterns abuse exactly the kind of access queryAPIKey gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for queryAPIKey:
{
"version": "1",
"default": "deny",
"tools": {
"queryAPIKey": {}
}
} queryAPIKey is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query comprehensive information about an API key. Use master or sub-account. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for queryAPIKey: 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.
queryAPIKey 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 queryAPIKey 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 queryAPIKey. 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.
queryAPIKey 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.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.