AI agents use set_spot_margin_auto_repay_mode 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 writes/modifies account settings (auto-repay mode for spot margin) but does not delete data or commit financial transactions directly. However, it has high severity because misconfiguration could lead to unintended automatic margin repayments, excessive fees, or forced liquidations if an AI agent sets this incorrectly without user intent.
From the tool's definition Tool name and description indicate 'Set spot margin auto repay mode' which modifies account margin settings. This is a reversible configuration change to the user's trading account that affects how margin interest is automatically repaid.
Attacks that exploit this kind of access
Set spot margin auto repay mode. 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 set_spot_margin_auto_repay_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 Bybit. Nothing to install.
set_spot_margin_auto_repay_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_spot_margin_auto_repay_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_spot_margin_auto_repay_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_spot_margin_auto_repay_mode 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 →