Query ADL (Auto-Deleveraging) alert data and insurance fund metrics for derivative contracts,\nindicating the current ADL risk level and activation thresholds.\n\nUse this endpoint when you need to:\n- Monitor ADL risk levels for specific contract symbols in real-time\n- Check the current insuran...
AI agents call getAdlAlert 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 tool retrieves and queries real-time ADL risk data and insurance fund metrics for informational purposes only. The use of 'Query' and 'Monitor' and 'Check' indicates read-only operations with no side effects. No data is created, modified, deleted, or financial transactions are executed. Misuse would only expose market risk information to the agent, with minimal blast radius.
From the tool's definition Tool name is 'getAdlAlert' and description states 'Query ADL alert data and insurance fund metrics' and 'Monitor ADL risk levels' and 'Check the current insurance fund balance' — all query/monitoring operations with no modifications.
Documented attack patterns abuse exactly the kind of access getAdlAlert 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 getAdlAlert:
{
"version": "1",
"default": "deny",
"tools": {
"getAdlAlert": {}
}
}getAdlAlert 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 ADL (Auto-Deleveraging) alert data and insurance fund metrics for derivative contracts,\nindicating the current ADL risk level and activation thresholds.\n\nUse this endpoint when you need to:\n- Monitor ADL risk levels for specific contract symbols in real-time\n- Check the current insurance fund balance (. 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 getAdlAlert: 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.
getAdlAlert 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 getAdlAlert 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 getAdlAlert. 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.
getAdlAlert 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.