Get all active (pending) TP/SL orders.
AI agents call get_pending_tpsl_orders 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 only queries existing TP/SL order data and returns it. It has no side effects, does not execute trades, does not move funds, and does not modify any orders. Although it exists within a financial trading context (BitUnix futures/spot exchange), the tool itself performs only information retrieval. The financial risk is contextual to the server's purpose, not intrinsic to this particular tool's action.
From the tool's definition get_pending_tpsl_orders retrieves pending take-profit/stop-loss orders with no modification or execution. The verb 'get' and the passive state ('pending orders') indicate a read operation.
Attacks that exploit this kind of access
Get all active (pending) TP/SL orders. 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_pending_tpsl_orders: 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_pending_tpsl_orders 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_pending_tpsl_orders 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_pending_tpsl_orders. 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_pending_tpsl_orders 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 →