Get closed/historical positions.
AI agents call get_history_positions 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 retrieves or queries closed/historical position data from the BitUnix exchange. It performs no write, execute, destructive, or financial operations—it simply fetches previously-closed position records for review. Even though it operates on a financial platform (trading exchange), the tool itself does not move money, create orders, modify positions, or trigger trades.
From the tool's definition Tool name 'get_history_positions' and description 'Get closed/historical positions' indicate a query operation that retrieves historical data without side effects.
Attacks that exploit this kind of access
Get closed/historical positions. 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_history_positions: 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_history_positions 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_history_positions 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_history_positions. 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_history_positions 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 →