Query recent public trading history for a symbol, returning execution records with\nprice, size, taker direction, timestamp, and sequence number.\n\nUse this endpoint when you need to:\n- Inspect recent trade flow and execution prices for a symbol\n- Retrieve trade records for display or analysis...
AI agents call getRecentPublicTrades 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 queries and returns historical trading data (price, size, direction, timestamp) for analysis and display purposes. It performs a read-only operation on public market data with no ability to modify, delete, execute transactions, or move funds. The verb 'Query' and 'Retrieve' confirm retrieval semantics. No mutation or financial commitment occurs.
From the tool's definition Tool name 'getRecentPublicTrades' and description 'Query recent public trading history' and 'Retrieve trade records for display or analysis purposes' indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access getRecentPublicTrades 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 getRecentPublicTrades:
{
"version": "1",
"default": "deny",
"tools": {
"getRecentPublicTrades": {}
}
} getRecentPublicTrades 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 recent public trading history for a symbol, returning execution records with\nprice, size, taker direction, timestamp, and sequence number.\n\nUse this endpoint when you need to:\n- Inspect recent trade flow and execution prices for a symbol\n- Retrieve trade records for display or analysis purposes\n- Correlate trades with orderbook data using the. 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 getRecentPublicTrades: 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.
getRecentPublicTrades 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 getRecentPublicTrades 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 getRecentPublicTrades. 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.
getRecentPublicTrades 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.