Reduce futures grid bot position.
AI agents use pionex_bot_futures_grid_reduce to commit financial operations through Pionex Trade — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
slippage | string | — | |
buOrderId | string | Yes | |
condition | string | — | |
reduceNum | number | Yes | |
conditionDirection | string | — |
Parameters from the server's own tool schema.
Reducing a futures grid bot position constitutes a financial operation as it involves closing or partially closing leveraged futures contracts, which has direct monetary consequences. This falls under Financial category as it commits or unwinds financial obligations in a live trading environment.
From the tool's definition 'Reduce futures grid bot position' — directly modifies an active futures trading position on a financial exchange
Attacks that exploit this kind of access
Reduce futures grid bot position. It is categorised as a Financial tool in the Pionex Trade MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
pionex_bot_futures_grid_reduce accepts 5 parameters: slippage, buOrderId, condition, reduceNum, conditionDirection. Required: buOrderId, reduceNum. The full parameter table on this page comes from the server's own tool schema.
Register the Pionex Trade MCP server in PolicyLayer and add a rule for pionex_bot_futures_grid_reduce: 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 Pionex Trade. Nothing to install.
pionex_bot_futures_grid_reduce is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pionex_bot_futures_grid_reduce 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 pionex_bot_futures_grid_reduce. 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.
pionex_bot_futures_grid_reduce is provided by the Pionex Trade MCP server (@pionex/pionex-trade-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 →