Toggle the auto-add-margin feature for a position. When enabled, the system automatically\nadds margin from available balance to prevent liquidation. Only works in isolated margin mode.\n\nAgent hint: Use this to toggle auto-add-margin on isolated margin positions. Set autoAddMargin to 1 (enable)...
AI agents use setAutoAddMargin to create or update resources in Bybit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.
This tool modifies account configuration settings (auto-add-margin feature toggling) in a reversible manner—the setting can be toggled back on or off. It does not execute arbitrary code, delete data permanently, or move funds directly, so it does not qualify as Execute, Destructive, or Financial.
From the tool's definition Tool description states 'Toggle the auto-add-margin feature' and 'Set autoAddMargin to 1 (enable) or 0 (disable)', indicating modification of account settings.
Documented attack patterns abuse exactly the kind of access setAutoAddMargin 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 setAutoAddMargin:
{
"version": "1",
"default": "deny",
"tools": {
"setAutoAddMargin": {
"limits": [
{
"counter": "setautoaddmargin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} setAutoAddMargin 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.
Toggle the auto-add-margin feature for a position. When enabled, the system automatically\nadds margin from available balance to prevent liquidation. Only works in isolated margin mode.\n\nAgent hint: Use this to toggle auto-add-margin on isolated margin positions. Set autoAddMargin to 1 (enable) or 0 (disable).\nOnly works for linear contracts in isolated margin mode. In hedge mode, specify positionIdx (1=buy, 2=sell). It is categorised as a Write tool in the Bybit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for setAutoAddMargin: 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.
setAutoAddMargin 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 setAutoAddMargin 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 setAutoAddMargin. 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.
setAutoAddMargin is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-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.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.