getClosePosition
Query closed option position data including entry/exit prices, fees, delivery details, and realized PnL.\nOnly applicable to option contracts.\n\nAgent hint: Use this to retrieve closed option positions. Only category=option is supported.\nDefault time range is 24 hours. Max range per query is 7 ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getcloseposition.md
What getClosePosition does on Bybit MCP Server
AI agents call getClosePosition to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getClosePosition is rated Low
The tool retrieves read-only information about past trading positions. The word 'Query' and absence of any write, execute, delete, or financial action verbs confirms this is a Read operation. While the server overall permits trading and financial transactions, this specific tool only retrieves historical data.
From the tool's definition Tool name 'getClosePosition' and description 'Query closed option position data' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getClosePosition safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getClosePosition, this is the rule to start with:
getClosePosition 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 MCP Server, apply this rule, and every getClosePosition call is checked against it from then on.
Questions about getClosePosition
Query closed option position data including entry/exit prices, fees, delivery details, and realized PnL.\nOnly applicable to option contracts.\n\nAgent hint: Use this to retrieve closed option positions. Only category=option is supported.\nDefault time range is 24 hours. Max range per query is 7 days. Supports up to 6 months of history.\nReturns entry/exit prices, delivery info, fees, and realized PnL. 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 getClosePosition: 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.
getClosePosition 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 getClosePosition 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 getClosePosition. 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.
getClosePosition 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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue