Query interest and borrowing records for the unified account. Supports filtering\nby currency and time range with pagination.\n\nRate limit: 5 req/s\n\nAgent hint: Use this to review borrowing costs and interest history. Filter by currency\n(USDC, USDT, BTC, ETH). Default returns 30 days if no ti...
AI agents call getBorrowHistory 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.
getBorrowHistory retrieves historical data about borrowing and interest from the unified account. The operation has no side effects—it only reads and returns existing records. While the server overall handles financial data and transactions, this specific tool is purely informational and read-only.
From the tool's definition Tool queries 'interest and borrowing records' with 'filtering by currency and time range' and 'pagination'. The description explicitly states it is used to 'review borrowing costs and interest history' without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access getBorrowHistory 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 getBorrowHistory:
{
"version": "1",
"default": "deny",
"tools": {
"getBorrowHistory": {}
}
}getBorrowHistory 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.
Query interest and borrowing records for the unified account. Supports filtering\nby currency and time range with pagination.\n\nRate limit: 5 req/s\n\nAgent hint: Use this to review borrowing costs and interest history. Filter by currency\n(USDC, USDT, BTC, ETH). Default returns 30 days if no time range is specified.\nMax 30-day span. Use cursor for pagination, limit max 50 per page. 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 getBorrowHistory: 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.
getBorrowHistory 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 getBorrowHistory 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 getBorrowHistory. 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.
getBorrowHistory 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.