getLiquidityMiningYieldRecords
Query yield claim records for Liquidity Mining positions with cursor-based pagination.\n\nRate Limit: 10 req/s (UID)
This record as markdown: /tools/bybit-exchange-trading-mcp/getliquidityminingyieldrecords.md
What getLiquidityMiningYieldRecords does on Bybit MCP Server
AI agents call getLiquidityMiningYieldRecords to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getLiquidityMiningYieldRecords is rated Low
This tool retrieves historical yield/claim records for liquidity mining positions. The verb 'Query' and 'get' prefix confirm it performs a read-only operation with no side effects—no data is created, modified, deleted, or financial transactions are executed. The rate limit (10 req/s) reflects query throttling, not destructive operations.
From the tool's definition Tool name 'getLiquidityMiningYieldRecords' and description 'Query yield claim records' indicate a retrieval operation. Cursor-based pagination is a typical pattern for querying historical data without modification.
Attacks that exploit this kind of access
The rule that runs getLiquidityMiningYieldRecords safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getLiquidityMiningYieldRecords, this is the rule to start with:
getLiquidityMiningYieldRecords is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every getLiquidityMiningYieldRecords call is checked against it from then on.
Questions about getLiquidityMiningYieldRecords
Query yield claim records for Liquidity Mining positions with cursor-based pagination.\n\nRate Limit: 10 req/s (UID). 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 getLiquidityMiningYieldRecords: 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.
getLiquidityMiningYieldRecords 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 getLiquidityMiningYieldRecords 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 getLiquidityMiningYieldRecords. 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.
getLiquidityMiningYieldRecords 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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue