Transfer positions between two unified trading accounts (UIDs) without fees.\nSupports linear, inverse, spot, and option. Up to 25 legs per request.\nBoth accounts must be under the same master account.\n\nAgent hint: Use this to move positions between sub-accounts. Requires master API key.\nBoth...
AI agents invoke movePosition to trigger actions in Bybit MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool transfers/moves trading positions between accounts, which is an external financial operation on a cryptocurrency exchange. While it doesn't directly move money, it repositions financial instruments (linear, inverse, spot, options) between accounts.
From the tool's definition Transfer positions between two unified trading accounts (UIDs) without fees... move positions between sub-accounts. Requires master API key.
Documented attack patterns abuse exactly the kind of access movePosition 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 movePosition:
{
"version": "1",
"default": "deny",
"tools": {
"movePosition": {
"limits": [
{
"counter": "moveposition_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}movePosition stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Transfer positions between two unified trading accounts (UIDs) without fees.\nSupports linear, inverse, spot, and option. Up to 25 legs per request.\nBoth accounts must be under the same master account.\n\nAgent hint: Use this to move positions between sub-accounts. Requires master API key.\nBoth UIDs must be UTA. Futures must be in one-way mode. Max 25 legs per request.\nPrice must be within 95%-105% of mark price for linear/inverse. No fees generated.\nCheck status via getMovePositionHistory if response status is Processing. It is categorised as a Execute tool in the Bybit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for movePosition: 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.
movePosition is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the movePosition 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 movePosition. 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.
movePosition 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.