[Transactions / Trades] 市場の約定履歴（transactions / recent trades）を取得。直近60件 or 日付指定。金額・価格でフィルタ可能。
AI agents call get_transactions to retrieve information from Bitbank Lab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical transaction data from the bitbank API without side effects. It reads past market data and trades (up to 60 recent records or date-filtered), allowing analysis but not execution of trades, movement of funds, or modification of data. The filtering parameters enable data retrieval refinement but do not alter the underlying data.
From the tool's definition Tool retrieves transaction/trade history data (市場の約定履歴 = market execution history / recent trades), supports filtering by date, amount, and price. No modification, deletion, or financial action is performed.
Attacks that exploit this kind of access
[Transactions / Trades] 市場の約定履歴（transactions / recent trades）を取得。直近60件 or 日付指定。金額・価格でフィルタ可能。. It is categorised as a Read tool in the Bitbank Lab MCP Server, which means it retrieves data without modifying state.
Register the Bitbank Lab MCP server in PolicyLayer and add a rule for get_transactions: 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 Bitbank Lab. Nothing to install.
get_transactions 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_transactions 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_transactions. 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_transactions is provided by the Bitbank Lab MCP server (tjackiet/bitbank-genesis-mcp-server-http-archive). 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 →