AI agents call get_spot_margin_max_borrowable to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves margin borrowing capacity information from the Bybit exchange. It is a getter/query operation with no side effects—it does not execute trades, modify account settings, delete data, or move funds. The action is purely informational, placing it squarely in the Read category. Severity is low because misuse would only expose information, not cause financial harm or data loss.
From the tool's definition Tool name 'get_spot_margin_max_borrowable' and description 'Get spot margin max borrowable amount' indicate a read-only query operation that retrieves information about margin borrowing limits without modifying any data.
Attacks that exploit this kind of access
Get spot margin max borrowable amount. 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_spot_margin_max_borrowable: 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_spot_margin_max_borrowable 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_spot_margin_max_borrowable 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_spot_margin_max_borrowable. 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_spot_margin_max_borrowable 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →