Query unified account wallet transaction logs. Supports filtering by category,\ncurrency, transaction type, and time range. Returns up to 2 years of historical data.\n\nRate limit: 5 req/s\n\nAgent hint: Use this to retrieve detailed wallet transaction history. Filter by category\n(spot/linear/op...
AI agents call getTransactionLog 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 is a straightforward read-only query tool that retrieves account transaction history without any side effects. No data is created, modified, deleted, or executed. The ability to filter historical transaction data over specified time ranges presents only low risk of misuse, as it cannot alter account state or initiate new transactions.
From the tool's definition Tool description states: "Query unified account wallet transaction logs" and "retrieve detailed wallet transaction history." The tool only queries and retrieves historical data with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access getTransactionLog 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 getTransactionLog:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactionLog": {}
}
}getTransactionLog 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 unified account wallet transaction logs. Supports filtering by category,\ncurrency, transaction type, and time range. Returns up to 2 years of historical data.\n\nRate limit: 5 req/s\n\nAgent hint: Use this to retrieve detailed wallet transaction history. Filter by category\n(spot/linear/option/inverse), currency, or type. Time range defaults to last 24h.\nMax 7-day span when both startTime and endTime are given. Use cursor for pagination.\nLimit max is 50 per page. 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 getTransactionLog: 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.
getTransactionLog 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 getTransactionLog 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 getTransactionLog. 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.
getTransactionLog 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.