AI agents call get_closed_pnl 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 historical profit/loss data without modifying, deleting, or executing any trades or financial transactions. It is a straightforward read operation on existing records. The low severity reflects minimal blast radius if misused — an AI agent could only retrieve historical data already accessible to the account holder, not alter positions or commit funds.
From the tool's definition Tool name is 'get_closed_pnl' and description states 'Get closed profit and loss records' — a pure retrieval operation with no side effects on account state or financial position.
Attacks that exploit this kind of access
Get closed profit and loss records. 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_pnl: 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_pnl 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_pnl 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_pnl. 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_pnl 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 →