New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_move_position_history

A read tool on the Bybit MCP server.

SERVERBybit SOURCEjohnnywic/bybit-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/get-move-position-history.md

What get_move_position_history does on Bybit

AI agents call get_move_position_history to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_move_position_history is rated Low

This tool retrieves historical data about position movements with no side effects. It follows the Read category pattern of fetching or querying existing data (get, history query). Even in a financial trading context, a read-only retrieval of past position history poses minimal risk compared to tools that modify orders, execute trades, or transfer funds.

From the tool's definition Tool name 'get_move_position_history' and description 'Get move position history' indicate a retrieval operation that queries historical position data without modifying or executing actions.

Questions about get_move_position_history

What does the get_move_position_history tool do? +

get_move_position_history is a read tool on the Bybit MCP server. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_move_position_history? +

Register the Bybit MCP server in PolicyLayer and add a rule for get_move_position_history: 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. Nothing to install.

What risk level is get_move_position_history? +

get_move_position_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_move_position_history? +

Yes. Add a rate_limit block to the get_move_position_history 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.

How do I block get_move_position_history completely? +

Set action: deny in the PolicyLayer policy for get_move_position_history. 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.

What MCP server provides get_move_position_history? +

get_move_position_history is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Bybit, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bybit's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.