Terminates an active strategy and cancels all associated pending orders.\n\nWhen to use:\n- Stop strategy before it completes naturally\n- React to changing market conditions\n- Cancel strategy that has unfavorable execution\n- Emergency stop for risk management\n\nWhat happens when you stop:\n1....
AI agents invoke stopStrategy 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 executes a command that triggers real-time effects on a live trading system: it terminates strategies and cancels pending orders. While the action itself is reversible (strategies can be restarted, new orders can be placed), it qualifies as Execute rather than Write because it invokes external system operations with immediate side effects on market positions and active trading logic.
From the tool's definition Terminates an active strategy and cancels all associated pending orders. Triggers external operations (strategy termination, order cancellation) whose effects depend on which strategy is targeted.
Documented attack patterns abuse exactly the kind of access stopStrategy 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 stopStrategy:
{
"version": "1",
"default": "deny",
"tools": {
"stopStrategy": {
"limits": [
{
"counter": "stopstrategy_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stopStrategy 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.
Terminates an active strategy and cancels all associated pending orders.\n\nWhen to use:\n- Stop strategy before it completes naturally\n- React to changing market conditions\n- Cancel strategy that has unfavorable execution\n- Emergency stop for risk management\n\nWhat happens when you stop:\n1. Strategy status → Terminated\n2. All pending orders → Canceled immediately\n3. Partially filled orders → Cancel remaining unfilled portion\n4. Filled orders → No change (remain as filled)\n5. Strategy execution stats → Preserved for history\n\nImportant notes:\n- Stopped strategies cannot be restarted\n- To continue, create a new strategy with remaining size\n- Strategy terminateType will be set to \. 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 stopStrategy: 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.
stopStrategy 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 stopStrategy 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 stopStrategy. 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.
stopStrategy 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.