AI agents call get_journal to retrieve information from Bybit Ws without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical trading data and computes analytical metrics. While it performs no data modification, the severity is 'medium' rather than 'low' because the analysis output could inform financial decisions that move capital (the sibling tools include place_entry and get_positions), and leaked trading journal data could expose sensitive trading strategies and performance history.
From the tool's definition Tool name is 'get_journal' and description states it retrieves and analyzes trading journal data: 'Get trading journal analysis: FIFO-matched roundtrips, win rate, profit/loss ratio, disposition effect, overtrading, chasing, anchoring biases, and alerts.' The…
Attacks that exploit this kind of access
Get trading journal analysis: FIFO-matched roundtrips, win rate, profit/loss ratio, disposition effect, overtrading, chasing, anchoring biases, and alerts. It is categorised as a Read tool in the Bybit Ws MCP Server, which means it retrieves data without modifying state.
Register the Bybit Ws MCP server in PolicyLayer and add a rule for get_journal: 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 Ws. Nothing to install.
get_journal 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_journal 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_journal. 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_journal is provided by the Bybit Ws MCP server (poliakarmai/bybit-ws). 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 →