AI agents call get_earn_yield_history 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 retrieves historical yield information from the Bybit exchange. It performs no modifications, deletions, executions, or financial transactions—it simply queries and returns data about past earn yields. The severity is low because misuse would at worst expose historical financial data without enabling unwanted state changes or transactions.
From the tool's definition Tool name 'get_earn_yield_history' and description 'Get Earn yield history' clearly indicate a retrieval operation with no side effects. The verb 'get' and the query-like nature of fetching historical yield data confirm this is a read-only operation.
Attacks that exploit this kind of access
Get Earn yield history. 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_earn_yield_history: 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_earn_yield_history 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_earn_yield_history 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_earn_yield_history. 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_earn_yield_history 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 →