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

get_position_info

Get detailed position information including size, value, PnL, and margin for your trading positions. Essential for portfolio monitoring and risk management.

SERVERBybit MCP Server SOURCEbcusack/bybit-py-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/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.

Questions about get_position_info

What does the get_position_info tool do? +

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.

How do I enforce a policy on get_position_info? +

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.

What risk level is get_position_info? +

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

Can I rate-limit get_position_info? +

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.

How do I block get_position_info completely? +

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.

What MCP server provides get_position_info? +

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.

// 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 MCP Server'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.