getCryptoLoanFlexibleRepaymentHistory
Query historical flexible repayment records with pagination.\n\nFeatures:\n- Query by repayment ID or currency\n- Pagination support\n- View repayment details including principal and interest\n- Rate limit: 5 requests per UID\n\nUse Cases:\n- Track repayment history\n- Verify repayment transactio...
This record as markdown: /tools/bybit-exchange-trading-mcp/getcryptoloanflexiblerepaymenthistory.md
What getCryptoLoanFlexibleRepaymentHistory does on Bybit MCP Server
AI agents call getCryptoLoanFlexibleRepaymentHistory to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getCryptoLoanFlexibleRepaymentHistory is rated Low
This tool retrieves historical financial data from the Bybit exchange without modifying any state or executing financial transactions. It is a pure query operation with pagination support for viewing past repayment records. The severity is low because misuse would only result in unauthorized viewing of account history, not financial loss or destructive action.
From the tool's definition The tool description explicitly states it is for "Query historical flexible repayment records" and "View repayment details".
Attacks that exploit this kind of access
The rule that runs getCryptoLoanFlexibleRepaymentHistory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCryptoLoanFlexibleRepaymentHistory, this is the rule to start with:
getCryptoLoanFlexibleRepaymentHistory 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 MCP Server, apply this rule, and every getCryptoLoanFlexibleRepaymentHistory call is checked against it from then on.
Questions about getCryptoLoanFlexibleRepaymentHistory
Query historical flexible repayment records with pagination.\n\nFeatures:\n- Query by repayment ID or currency\n- Pagination support\n- View repayment details including principal and interest\n- Rate limit: 5 requests per UID\n\nUse Cases:\n- Track repayment history\n- Verify repayment transactions\n- Calculate total interest paid. 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 getCryptoLoanFlexibleRepaymentHistory: 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.
getCryptoLoanFlexibleRepaymentHistory 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 getCryptoLoanFlexibleRepaymentHistory 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 getCryptoLoanFlexibleRepaymentHistory. 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.
getCryptoLoanFlexibleRepaymentHistory 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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue