This record as markdown: /tools/johnnywic-bybit-mcp/get-broker-account-info.md
What get_broker_account_info does on Bybit
AI agents call get_broker_account_info to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_broker_account_info is rated Low
This tool retrieves broker account information, which is a read-only operation with no side effects. It does not create, modify, delete, or execute code. While the broader server enables financial trading operations, this specific tool is limited to querying account data. The severity is low because unauthorized access to account info is a data breach risk but has no direct financial impact on its own.
From the tool's definition Tool name 'get_broker_account_info' and description 'Get broker account info' indicate a retrieval operation that queries account information without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs get_broker_account_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_broker_account_info, this is the rule to start with:
get_broker_account_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every get_broker_account_info call is checked against it from then on.
Questions about get_broker_account_info
get_broker_account_info is a read tool on the Bybit MCP server. 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_broker_account_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_broker_account_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_broker_account_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_broker_account_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_broker_account_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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue