Get all spot wallet balances (separate from futures account).
AI agents call get_spot_account to retrieve information from Bitunix MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves financial account data (spot wallet balances) but does not modify, execute transactions, or commit financial obligations. It is a read-only information retrieval operation. While the broader server context involves financial trading, this specific tool only reads data without executing trades or moving money, making it a Read-category risk with low severity.
From the tool's definition Tool name is 'get_spot_account' and description states 'Get all spot wallet balances'. The verb 'Get' and action of retrieving/querying account balances with 'no side effects' are the defining characteristics of a Read operation.
Attacks that exploit this kind of access
Get all spot wallet balances (separate from futures account). It is categorised as a Read tool in the Bitunix MCP MCP Server, which means it retrieves data without modifying state.
Register the Bitunix MCP server in PolicyLayer and add a rule for get_spot_account: 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 Bitunix MCP. Nothing to install.
get_spot_account 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_spot_account 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_spot_account. 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_spot_account is provided by the Bitunix MCP server (luiinventions/bitunix-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 →