This record as markdown: /tools/johnnywic-bybit-mcp/get-adl-alert.md
What get_adl_alert does on Bybit
AI agents call get_adl_alert to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_adl_alert is rated Low
This is a read-only query that retrieves alert information from the Bybit exchange. It has no side effects on account state, positions, or balances. Even in a trading context, information retrieval carries minimal risk. The low severity reflects that misuse would only expose data the user already has access to.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get ADL alert info' queries existing data about Auto-Deleveraging alerts without modifying state, triggering trades, or moving funds.
Attacks that exploit this kind of access
The rule that runs get_adl_alert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_adl_alert, this is the rule to start with:
get_adl_alert 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, apply this rule, and every get_adl_alert call is checked against it from then on.
Questions about get_adl_alert
Get ADL (Auto-Deleveraging) alert info. 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_adl_alert: 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_adl_alert 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_adl_alert 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_adl_alert. 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_adl_alert 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue