get_instruments_info

Get trading instruments information

SERVERBybit MCP Server SOURCEbcusack/bybit-py-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bcusack-bybit-py-mcp/get-instruments-info.md

WHAT IT DOES

What get_instruments_info does on Bybit MCP Server

AI agents call get_instruments_info to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_instruments_info is rated Low

This is a pure data retrieval operation. It queries static or semi-static instrument metadata from the exchange. There is no capability to execute trades, modify orders, delete data, or move funds. Even if an AI agent misuses this tool, the worst outcome is receiving irrelevant instrument data, which poses minimal risk. The low severity reflects the absence of any destructive or financial impact potential.

From the tool's definition Tool name 'get_instruments_info' and description 'Get trading instruments information' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_instruments_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_instruments_info, this is the rule to start with:

get_instruments_info Allowed

get_instruments_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_instruments_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every get_instruments_info call is checked against it from then on.

FAQ

Questions about get_instruments_info

What does the get_instruments_info tool do? +

Get trading instruments information. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_instruments_info? +

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.

What risk level is get_instruments_info? +

get_instruments_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_instruments_info? +

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.

How do I block get_instruments_info completely? +

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.

What MCP server provides get_instruments_info? +

get_instruments_info is provided by the Bybit MCP Server MCP server (bcusack/bybit-py-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bybit MCP Server, and thousands of servers like it.

This server

All 36 Bybit MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →