AI agents call get_my_deposit_withdrawal to retrieve information from Bitbank without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_my_deposit_withdrawal only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
[Deposit / Withdrawal / Transfer History] 入出金・入出庫の履歴（deposit / withdrawal / transfer / funding history）を取得。JPY入出金+暗号資産入出庫に対応。全件取得可能。Private API。. It is categorised as a Read tool in the Bitbank MCP Server, which means it retrieves data without modifying state.
Register the Bitbank MCP server in PolicyLayer and add a rule for get_my_deposit_withdrawal: 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. Nothing to install.
get_my_deposit_withdrawal 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_deposit_withdrawal 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_deposit_withdrawal. 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_deposit_withdrawal is provided by the Bitbank MCP server (tjackiet/bitbank-lab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.