AI agents use move_position to create or update resources in Bybit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit environment.
While 'move_position' modifies account state by transferring positions between user IDs, it is reversible (positions can be moved back). This makes it Write rather than Destructive. However, the high blast radius—transferring trading positions between accounts could redirect profits/losses or enable unauthorized account manipulation—warrants high severity.
From the tool's definition Tool name 'move_position' combined with description 'Move positions between UIDs (master API key only)' indicates modification of position ownership/location. The master API key requirement and cross-UID transfer imply significant account-level changes.
Attacks that exploit this kind of access
Move positions between UIDs (master API key only). It is categorised as a Write tool in the Bybit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP server in PolicyLayer and add a rule for move_position: 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.
move_position is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_position 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 move_position. 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.
move_position 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.
move_position is one line of Bybit's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →