Query tiered risk limit parameters for perpetual and futures contracts, including\nposition size limits, initial/maintenance margin rates, and maximum leverage per tier.\n\nUse this endpoint when you need to:\n- Understand the risk tiers for a contract before placing large positions\n- Retrieve m...
AI agents call getRiskLimit 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 risk limit parameters, leverage tiers, and margin rates from the Bybit exchange. It performs a read-only lookup operation with no side effects—no positions are opened, no orders placed, no balances modified, and no financial transactions executed. The tool simply returns informational data to help users understand trading constraints before taking action.
From the tool's definition Tool name is 'getRiskLimit' and description states 'Query tiered risk limit parameters' and 'Retrieve maximum leverage allowed'. The verb 'Query' and 'Retrieve' indicate data retrieval with no modifications.
Documented attack patterns abuse exactly the kind of access getRiskLimit 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 getRiskLimit:
{
"version": "1",
"default": "deny",
"tools": {
"getRiskLimit": {}
}
}getRiskLimit 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 tiered risk limit parameters for perpetual and futures contracts, including\nposition size limits, initial/maintenance margin rates, and maximum leverage per tier.\n\nUse this endpoint when you need to:\n- Understand the risk tiers for a contract before placing large positions\n- Retrieve maximum leverage allowed at each risk tier (. 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 getRiskLimit: 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.
getRiskLimit 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 getRiskLimit 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 getRiskLimit. 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.
getRiskLimit 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.