AI agents call get_new_crypto_loan_collateral_data 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 queries/retrieves data about crypto loan collateral coins. It has no side effects on accounts, positions, or finances. The 'get' pattern combined with a data retrieval description clearly indicates a Read operation. On a financial trading platform, data retrieval about loan collateral is low severity because it does not move money, execute trades, or modify any state.
From the tool's definition Tool name 'get_new_crypto_loan_collateral_data' uses the verb 'get', and the description states it retrieves ('Get') collateral coin data with no indication of modification, deletion, or execution of trades.
Attacks that exploit this kind of access
Get new crypto loan collateral coin data. 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_new_crypto_loan_collateral_data: 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_new_crypto_loan_collateral_data 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_new_crypto_loan_collateral_data 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_new_crypto_loan_collateral_data. 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_new_crypto_loan_collateral_data 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 →