Retrieve unified account configuration including margin mode, account status,\nand feature settings. No parameters required.\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check account configuration before performing operations that depend\non margin mode or account type. The unifiedMarginSt...
AI agents call getAccountInfo 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 only queries and retrieves existing account information without side effects. It returns read-only configuration data (marginMode, account status, UTA version) to inform downstream decisions. While it provides sensitive account details, it does not execute trades, modify settings, transfer funds, or delete data, classifying it unambiguously as a Read operation with low severity risk.
From the tool's definition Tool retrieves account configuration including margin mode, account status, and feature settings with no parameters required. Description explicitly states it is used to 'check account configuration' before operations.
Documented attack patterns abuse exactly the kind of access getAccountInfo gives an agent:
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 getAccountInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getAccountInfo": {}
}
}getAccountInfo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve unified account configuration including margin mode, account status,\nand feature settings. No parameters required.\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check account configuration before performing operations that depend\non margin mode or account type. The unifiedMarginStatus field indicates the UTA\nversion: 4 = UTA 2.0, 5 = UTA 2.0, 6 = UTA Pro. Check marginMode to confirm\nISOLATED_MARGIN, REGULAR_MARGIN, or PORTFOLIO_MARGIN. 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 getAccountInfo: 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.
getAccountInfo 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 getAccountInfo 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 getAccountInfo. 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.
getAccountInfo 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.
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.