AI agents call get_crypto_loan_adjustment_history 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 historical adjustment records for crypto loans. It is a read-only operation that poses minimal risk—it accesses past data with no capability to create, modify, delete, or execute trades. The blast radius of misuse is low since exposing historical loan adjustment data does not directly impact account security, enable unauthorized transactions, or cause financial harm.
From the tool's definition Tool name 'get_crypto_loan_adjustment_history' and description 'Get crypto loan LTV adjustment history' indicate a retrieval operation that queries historical data without modifying or executing transactions.
Attacks that exploit this kind of access
Get crypto loan LTV adjustment history. 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_crypto_loan_adjustment_history: 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_crypto_loan_adjustment_history 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_crypto_loan_adjustment_history 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_crypto_loan_adjustment_history. 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_crypto_loan_adjustment_history 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 →