get_spread_recent_trades
Get spread trading recent public trades.
This record as markdown: /tools/johnnywic-bybit-mcp/get-spread-recent-trades.md
What get_spread_recent_trades does on Bybit
AI agents call get_spread_recent_trades to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_spread_recent_trades is rated Low
This tool retrieves historical trade data from spread trading markets. It performs no modifications, deletions, or external operations—it only queries and returns existing public information. Despite being on a financial exchange server, the tool itself does not move money, execute trades, or change state; it merely reads market data. Therefore, it is classified as Read with low severity.
From the tool's definition Tool name 'get_spread_recent_trades' and description 'Get spread trading recent public trades' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_spread_recent_trades safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_spread_recent_trades, this is the rule to start with:
get_spread_recent_trades 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, apply this rule, and every get_spread_recent_trades call is checked against it from then on.
Questions about get_spread_recent_trades
Get spread trading recent public trades. 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_spread_recent_trades: 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_spread_recent_trades 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_spread_recent_trades 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_spread_recent_trades. 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_spread_recent_trades 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue