Change position mode between Hedge Mode and One-way Mode. HEDGE: Can hold both LONG and SHORT positions simultaneously. ONE-WAY: Only one direction at a time (positionSide=BOTH).
AI agents invoke BinanceFuturesChangePositionMode to trigger actions in Sperax Ecosystem Crypto & DeFI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool modifies trading account configuration on Binance Futures, affecting how positions can be held. While it doesn't directly move money, changing position mode can impact open positions and trading behavior, potentially causing liquidations or unexpected position closures.
From the tool's definition Change position mode between Hedge Mode and One-way Mode. HEDGE: Can hold both LONG and SHORT positions simultaneously. ONE-WAY: Only one direction at a time
Documented attack patterns abuse exactly the kind of access BinanceFuturesChangePositionMode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceFuturesChangePositionMode:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceFuturesChangePositionMode": {
"limits": [
{
"counter": "binancefutureschangepositionmode_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}BinanceFuturesChangePositionMode stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Change position mode between Hedge Mode and One-way Mode. HEDGE: Can hold both LONG and SHORT positions simultaneously. ONE-WAY: Only one direction at a time (positionSide=BOTH). It is categorised as a Execute tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for BinanceFuturesChangePositionMode: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
BinanceFuturesChangePositionMode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the BinanceFuturesChangePositionMode 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 BinanceFuturesChangePositionMode. 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.
BinanceFuturesChangePositionMode is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.