Query position tier data for spot margin trading.\n- Returns tier information including borrow limits, margin rates, and max leverage.\n- If
AI agents call getPositionTiers 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 existing position tier configuration data from the Bybit exchange. It performs a read-only operation that returns informational metadata about trading tiers. No data is created, modified, deleted, or financial transactions are executed. Misuse would have minimal impact as it only exposes existing, non-sensitive tier structures already known to the trading platform.
From the tool's definition Tool name 'getPositionTiers' and description 'Query position tier data' — uses 'Query' verb indicating data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access getPositionTiers 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 getPositionTiers:
{
"version": "1",
"default": "deny",
"tools": {
"getPositionTiers": {}
}
} getPositionTiers 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 position tier data for spot margin trading.\n- Returns tier information including borrow limits, margin rates, and max leverage.\n- If. 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 getPositionTiers: 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.
getPositionTiers 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 getPositionTiers 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 getPositionTiers. 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.
getPositionTiers 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.