Switch between cross margin (uses entire account balance as collateral) and isolated margin (uses only position margin). Cross margin has lower liquidation risk but affects entire account.
AI agents invoke switch_cross_isolated_margin to trigger actions in Bybit 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 changes the margin mode for trading positions, which is an operational change that affects how collateral is allocated and liquidation risk is managed. It doesn't directly move money or delete data, but it triggers a significant account-level configuration change that can affect the entire account balance used as collateral.
From the tool's definition Switch between cross margin (uses entire account balance as collateral) and isolated margin (uses only position margin). Cross margin has lower liquidation risk but affects entire account.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access switch_cross_isolated_margin gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for switch_cross_isolated_margin:
{
"version": "1",
"default": "deny",
"tools": {
"switch_cross_isolated_margin": {
"limits": [
{
"counter": "switch_cross_isolated_margin_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}switch_cross_isolated_margin 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.
Switch between cross margin (uses entire account balance as collateral) and isolated margin (uses only position margin). Cross margin has lower liquidation risk but affects entire account. It is categorised as a Execute tool in the Bybit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for switch_cross_isolated_margin: 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 Bybit MCP Server. Nothing to install.
switch_cross_isolated_margin 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 switch_cross_isolated_margin 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 switch_cross_isolated_margin. 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.
switch_cross_isolated_margin is provided by the Bybit MCP Server MCP server (bcusack/bybit-py-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bybit 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.
36 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.