Low Risk

getAccountInstruments

Query tradable instrument specifications for the user

How to control getAccountInstruments ↓

What getAccountInstruments does on Bybit MCP Server

AI agents call getAccountInstruments 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.

Low Risk

Why getAccountInstruments needs a policy

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.

Documented attack patterns abuse exactly the kind of access getAccountInstruments gives an agent:

How to control getAccountInstruments

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAccountInstruments": {}
  }
}

getAccountInstruments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Bybit MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Bybit MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.