Switch between One-way Mode and Hedge Mode for the account.
AI agents use set_position_mode to create or update resources in Mcp Binance Futures — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Binance Futures environment.
This tool modifies account-level trading configuration (position mode). While reversible in principle, switching position modes on a live futures account can affect how existing positions and orders behave, potentially causing unintended liquidations or mismanaged hedges. It's a Write operation with high severity due to the blast radius on active trading positions if misused by an AI agent.
From the tool's definition Switch between One-way Mode and Hedge Mode for the account
Documented attack patterns abuse exactly the kind of access set_position_mode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Binance Futures, and nothing reaches the server without passing your rules. This is the rule we recommend for set_position_mode:
{
"version": "1",
"default": "deny",
"tools": {
"set_position_mode": {
"limits": [
{
"counter": "set_position_mode_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_position_mode stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Switch between One-way Mode and Hedge Mode for the account. It is categorised as a Write tool in the Mcp Binance Futures MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Binance Futures MCP server in PolicyLayer and add a rule for set_position_mode: 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 Mcp Binance Futures. Nothing to install.
set_position_mode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_position_mode 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 set_position_mode. 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.
set_position_mode is provided by the Mcp Binance Futures MCP server (muvon/mcp-binance-futures). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Binance Futures, 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.
23 Mcp Binance Futures tools catalogued and risk-classified — across an index of 43,000+ MCP servers.