get_position_info
Get detailed position information including size, value, PnL, and margin for your trading positions. Essential for portfolio monitoring and risk management.
This record as markdown: /tools/bcusack-bybit-py-mcp/get-position-info.md
What get_position_info does on Bybit MCP Server
AI agents call get_position_info 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 get_position_info is rated Low
This is a query/retrieval operation that returns account position data without side effects. While the Bybit server has financial capabilities overall, this specific tool only reads existing position data. Severity is low because the information retrieved is static account state that an AI agent could view without causing financial harm.
From the tool's definition Tool retrieves position information (size, value, PnL, margin) for monitoring purposes. No modification, deletion, or financial transaction occurs. Description emphasizes 'monitoring and risk management' without mentioning order execution or state changes.
Attacks that exploit this kind of access
The rule that runs get_position_info 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 get_position_info, this is the rule to start with:
get_position_info 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 get_position_info call is checked against it from then on.
Questions about get_position_info
Get detailed position information including size, value, PnL, and margin for your trading positions. Essential for portfolio monitoring and risk management. 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 get_position_info: 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.
get_position_info 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 get_position_info 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 get_position_info. 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.
get_position_info is provided by the Bybit MCP Server MCP server (bcusack/bybit-py-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