AI agents use toggle_spot_margin_trade to create or update resources in Bybit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit environment.
This tool enables or disables spot margin trading on the account. It modifies account settings in a reversible way (it can be toggled back), so it falls under Write rather than Destructive. However, the severity is high because enabling margin trading can expose the account to significant financial risk — leveraged positions can lead to liquidation and substantial losses if an AI agent misuses this capability.
From the tool's definition Toggle spot margin trading on or off
Attacks that exploit this kind of access
Toggle spot margin trading on or off. It is categorised as a Write tool in the Bybit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP server in PolicyLayer and add a rule for toggle_spot_margin_trade: 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. Nothing to install.
toggle_spot_margin_trade 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 toggle_spot_margin_trade 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 toggle_spot_margin_trade. 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.
toggle_spot_margin_trade is provided by the Bybit MCP server (johnnywic/bybit-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 →