Query historical collateral adjustment operations with pagination support.\n\nFeatures:\n- Private endpoint (authentication required)\n- Query by specific adjustId or filter by currency\n- Pagination support with cursor-based navigation\n- Shows before/after LTV for each adjustment\n- Track adjus...
AI agents call getCryptoLoanCommonAdjustmentHistory 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 is a data retrieval tool that queries historical records of collateral adjustments on the Bybit platform. It provides lookups, filtering, and pagination but does not create, modify, delete, or execute any operations.
From the tool's definition Tool description explicitly states 'Query historical collateral adjustment operations' and 'Review past collateral adjustments' — these are retrieval operations.
Documented attack patterns abuse exactly the kind of access getCryptoLoanCommonAdjustmentHistory 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 getCryptoLoanCommonAdjustmentHistory:
{
"version": "1",
"default": "deny",
"tools": {
"getCryptoLoanCommonAdjustmentHistory": {}
}
}getCryptoLoanCommonAdjustmentHistory 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 historical collateral adjustment operations with pagination support.\n\nFeatures:\n- Private endpoint (authentication required)\n- Query by specific adjustId or filter by currency\n- Pagination support with cursor-based navigation\n- Shows before/after LTV for each adjustment\n- Track adjustment status (processing, success, failed)\n- Rate limit: 5 requests per time window per UID\n\nUse Cases:\n- Review past collateral adjustments\n- Track LTV changes over time\n- Verify adjustment operations\n- Audit collateral management activities\n\nQuery Modes:\n- By adjustId: Get specific adjustment (no pagination)\n- By currency: Get all adjustments for a currency (with pagination)\n- All adjustments: Get complete history (with pagination). 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 getCryptoLoanCommonAdjustmentHistory: 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.
getCryptoLoanCommonAdjustmentHistory 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 getCryptoLoanCommonAdjustmentHistory 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 getCryptoLoanCommonAdjustmentHistory. 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.
getCryptoLoanCommonAdjustmentHistory 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.