Query closed PnL records for the current user. Results include entry/exit prices,\nfees, leverage, and realized PnL for each closed position.\n\nAgent hint: Use this to retrieve historical closed position PnL. Supports up to 730 days of data.\nMax 7-day range per query. Results are sorted newest ...
AI agents call getClosedPnl to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical financial data (closed position records) without modifying, creating, or deleting any data. While it relates to a financial platform, it does not move money, create financial obligations, or execute trades — it merely returns read-only historical records. The blast radius of misuse is minimal as the agent can only access the current user's own closed PnL history.
From the tool's definition Tool description states 'Query closed PnL records' and 'retrieve historical closed position PnL' — this is a data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access getClosedPnl gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getClosedPnl:
{
"version": "1",
"default": "deny",
"tools": {
"getClosedPnl": {}
}
}getClosedPnl is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query closed PnL records for the current user. Results include entry/exit prices,\nfees, leverage, and realized PnL for each closed position.\n\nAgent hint: Use this to retrieve historical closed position PnL. Supports up to 730 days of data.\nMax 7-day range per query. Results are sorted newest first. Use cursor for pagination.\nEach record includes entry/exit prices, PnL, fees, and leverage. 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 getClosedPnl: 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.
getClosedPnl 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 getClosedPnl 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 getClosedPnl. 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.
getClosedPnl is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.