Get exchange information
AI agents call get_instruments_info 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 retrieves static or near-static exchange metadata such as instrument specifications, trading rules, or market conditions. It performs no writes, deletions, trades, or external operations—purely informational query. Severity is low because misuse cannot cause financial loss, data corruption, or account damage.
From the tool's definition Tool name 'get_instruments_info' and description 'Get exchange information' indicate data retrieval with no modification or side effects. The verb 'get' and context of 'exchange information' (market data) confirm read-only operation.
Attacks that exploit this kind of access
Get exchange information. 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 get_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 MCP Server. Nothing to install.
get_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_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_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_instruments_info is provided by the Bybit MCP Server MCP server (kondisettyravi/mcp-bybit-node). 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 →