getAccountInstruments

Query tradable instrument specifications for the user

SERVERBybit MCP Server SOURCEbybit-exchange/trading-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/bybit-exchange-trading-mcp/getaccountinstruments.md

WHAT IT DOES

What getAccountInstruments does on Bybit MCP Server

AI agents call getAccountInstruments 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 getAccountInstruments is rated Low

This tool retrieves static or semi-static data about tradable instruments (specifications like contract sizes, tick sizes, leverage limits, etc.) available to the user's account. It is a read-only operation with no side effects—it neither modifies data, executes trades, moves funds, nor deletes anything.

From the tool's definition Tool name 'getAccountInstruments' and description 'Query tradable instrument specifications' indicate a retrieval operation. The verb 'Query' and noun 'specifications' denote data retrieval with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getAccountInstruments 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 getAccountInstruments, this is the rule to start with:

getAccountInstruments Allowed

getAccountInstruments 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": {
    "getAccountInstruments": {}
  }
}

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 getAccountInstruments call is checked against it from then on.

FAQ

Questions about getAccountInstruments

What does the getAccountInstruments tool do? +

Query tradable instrument specifications for the user. 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 getAccountInstruments? +

Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getAccountInstruments: 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 getAccountInstruments? +

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

Can I rate-limit getAccountInstruments? +

Yes. Add a rate_limit block to the getAccountInstruments 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 getAccountInstruments completely? +

Set action: deny in the PolicyLayer policy for getAccountInstruments. 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 getAccountInstruments? +

getAccountInstruments 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.

KEEP EXPLORING

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

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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