Query real-time position data such as PnL, leverage, liquidation price, and margin info.\nSupports linear (USDT/USDC perpetual and futures), inverse (perpetual and futures), and option contracts.\n\nAgent hint: Use this endpoint to check current open positions. For linear/inverse, specify categor...
AI agents call getPositionInfo 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 displays position information (PnL, leverage, liquidation price, margin info) without modifying, creating, deleting, or executing any operations. It is a straightforward read operation against the Bybit API. While the context involves financial assets, the tool itself performs only information queries, not financial transactions.
From the tool's definition Tool name is 'getPositionInfo' and description states 'Query real-time position data' — the verb 'query' and action 'check current open positions' indicate read-only data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access getPositionInfo 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 getPositionInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getPositionInfo": {}
}
}getPositionInfo 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 real-time position data such as PnL, leverage, liquidation price, and margin info.\nSupports linear (USDT/USDC perpetual and futures), inverse (perpetual and futures), and option contracts.\n\nAgent hint: Use this endpoint to check current open positions. For linear/inverse, specify category and either symbol or settleCoin.\nFor options, use baseCoin to filter by underlying asset. Response includes leverage, liquidation price, unrealized PnL, and margin details. 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 getPositionInfo: 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.
getPositionInfo 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 getPositionInfo 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 getPositionInfo. 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.
getPositionInfo 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.