This record as markdown: /tools/johnnywic-bybit-mcp/get-insurance.md
What get_insurance does on Bybit
AI agents call get_insurance 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_insurance is rated Low
This tool retrieves insurance pool information from the Bybit exchange without modifying, executing, or deleting anything. It is a straightforward data query operation with no blast radius if misused by an AI agent—at worst, it exposes public or account-accessible market data.
From the tool's definition Tool name 'get_insurance' and description 'Get insurance pool data' indicate data retrieval with no side effects. The verb 'Get' and lack of any modifying language confirm a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_insurance 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_insurance, this is the rule to start with:
get_insurance 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_insurance call is checked against it from then on.
Questions about get_insurance
Get insurance pool 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_insurance: 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_insurance 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_insurance 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_insurance. 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_insurance 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