[Orders Info / Bulk Order Status] 複数の注文IDの詳細情報を一括取得（最大100件）。ステータス・約定状況を一度に確認できる。Private API。
AI agents call get_orders_info 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 retrieves order information and status without modifying, deleting, or executing trades. While it accesses sensitive private account data (order details, execution status) which warrants medium severity due to potential data leakage or unauthorized surveillance of trading activity, the action itself is read-only.
From the tool's definition Tool name: get_orders_info; Description: 複数の注文IDの詳細情報を一括取得（最大100件）。ステータス・約定状況を一度に確認できる [Retrieves bulk order status and execution details for up to 100 orders]. Marked as 'Private API' indicating authentication-protected access to user account data.
Attacks that exploit this kind of access
[Orders Info / Bulk Order Status] 複数の注文IDの詳細情報を一括取得（最大100件）。ステータス・約定状況を一度に確認できる。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_orders_info: 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_orders_info 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_orders_info 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_orders_info. 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_orders_info 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 →