[My Trades / Trade History / Fills] 自分の現物約定履歴（my trades / trade history / fills / executions）を取得。通貨ペア・期間・件数でフィルタ可能。Private API。
AI agents call get_my_trade_history 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 is a data retrieval operation with no side effects—it queries past trading activity accessible only to an authenticated user. While it accesses sensitive financial transaction history (warranting medium severity due to the private financial information exposed), it does not create transactions, modify balances, execute trades, or move funds. The most severe category applicable is Read.
From the tool's definition Tool returns 'my trades / trade history / fills / executions' (自分の現物約定履歴) — historical transaction records that the user has already executed. Description states it is a 'Private API' that retrieves and filters data by currency pair, period, and count.
Attacks that exploit this kind of access
[My Trades / Trade History / Fills] 自分の現物約定履歴（my trades / trade history / fills / executions）を取得。通貨ペア・期間・件数でフィルタ可能。Private API。. 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_my_trade_history: 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_my_trade_history 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_my_trade_history 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_my_trade_history. 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_my_trade_history 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 →