getMovePositionHistory
Query the history of position move (block trade) orders.\nReturns order details, execution status, fees, and rejection info.\n\nAgent hint: Use this to check status and history of move position requests. Filter by category, symbol, status, or blockTradeId.\nMax 7-day range per query. Each record ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getmovepositionhistory.md
What getMovePositionHistory does on Bybit MCP Server
AI agents call getMovePositionHistory 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 getMovePositionHistory is rated Low
This tool retrieves and reads historical data about completed or in-progress block trade orders without modifying, deleting, or executing new trades. It is a pure data retrieval operation with no side effects. While it relates to financial activity (cryptocurrency trading), it only reads historical information rather than moving money or committing financial obligations.
From the tool's definition Tool queries history of position move orders and returns order details, execution status, fees, and rejection info.
Attacks that exploit this kind of access
The rule that runs getMovePositionHistory 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 getMovePositionHistory, this is the rule to start with:
getMovePositionHistory 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 getMovePositionHistory call is checked against it from then on.
Questions about getMovePositionHistory
Query the history of position move (block trade) orders.\nReturns order details, execution status, fees, and rejection info.\n\nAgent hint: Use this to check status and history of move position requests. Filter by category, symbol, status, or blockTradeId.\nMax 7-day range per query. Each record shows maker/taker side, execution details, and result codes.\nstatus=Processing means still executing; Filled means complete; Rejected means failed. 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 getMovePositionHistory: 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.
getMovePositionHistory 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 getMovePositionHistory 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 getMovePositionHistory. 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.
getMovePositionHistory 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