AI agents call get_closed_options_positions to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves closed options position history from the Bybit exchange. It performs no state changes, creates no transactions, executes no orders, and deletes no data. It is purely informational retrieval, fitting the Read category. Severity is low because misuse would only expose account history data, not enable financial transactions or destructive actions.
From the tool's definition Tool name 'get_closed_options_positions' and description 'Get closed options positions' indicate a retrieval operation with no side effects. The verb 'get' and action of retrieving historical position data are characteristic of read-only queries.
Attacks that exploit this kind of access
Get closed options positions. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_closed_options_positions: 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.
get_closed_options_positions 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_closed_options_positions 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_closed_options_positions. 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_closed_options_positions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →