AI agents call get_account_instruments_info 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 queries and retrieves account configuration data about tradable instruments. It performs no mutations, executions, or side effects—it only reads and returns information about what instruments are available for trading on the user's account. While it provides potentially sensitive account information, the blast radius of misuse is limited to information disclosure, justifying 'low' severity.
From the tool's definition Tool name and description indicate retrieval: 'Get account-level instruments info' and 'tradable instruments for your account'. The verb 'Get' and the absence of modification language confirm read-only data retrieval.
Attacks that exploit this kind of access
Get account-level instruments info (tradable instruments for your 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_account_instruments_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_account_instruments_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_account_instruments_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_account_instruments_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_account_instruments_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.
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 →