[Order Detail / Order Status] 指定した注文IDの詳細情報を取得。ステータス・約定状況・価格を確認できる。Private API。
AI agents call get_order 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 existing order information by ID and returns details such as status, execution status, and price. It is a read-only operation that retrieves data with no side effects. The Private API designation indicates user authentication is required, but the operation itself does not create, modify, delete, or execute trades—it only fetches information about an existing order.
From the tool's definition Tool description states '詳細情報を取得' (retrieve detailed information) and 'ステータス・約定状況・価格を確認できる' (can check status, execution status, and price). The tool retrieves order details using Private API without modifying or executing transactions.
Attacks that exploit this kind of access
[Order Detail / Order Status] 指定した注文IDの詳細情報を取得。ステータス・約定状況・価格を確認できる。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_order: 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_order 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_order 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_order. 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_order 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 →