AI agents call btse_get_wallet_history to retrieve information from Btse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays past wallet transaction records. It has no side effects, does not execute trades or commands, does not modify data, and does not move money. While it provides sensitive financial information, the action itself is non-destructive read-only access to historical data, which is the lowest risk category. The tool operates on live/testnet accounts but only performs queries.
From the tool's definition Tool name 'btse_get_wallet_history' and description 'Get wallet transaction history (deposits, withdrawals, PnL)' indicate a retrieval operation that queries historical transaction data without modifying or executing any actions.
Attacks that exploit this kind of access
Get wallet transaction history (deposits, withdrawals, PnL). It is categorised as a Read tool in the Btse MCP Server, which means it retrieves data without modifying state.
Register the Btse MCP server in PolicyLayer and add a rule for btse_get_wallet_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 Btse. Nothing to install.
btse_get_wallet_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 btse_get_wallet_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 btse_get_wallet_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.
btse_get_wallet_history is provided by the Btse MCP server (xbotlive/btse-mcp). 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 →