AI agents invoke stopSubscription 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 an operation that closes subscriptions and deallocates resources. While not creating, modifying, or deleting persistent data, it triggers an external system action (WebSocket termination) whose effects depend on which subscription ID is targeted.
From the tool's definition Tool name 'stopSubscription' and description indicate it terminates WebSocket connections and releases buffers ('关闭指定订阅，释放 WebSocket 连接和缓冲区'). This is a state-changing operation that manipulates active connections.
Documented attack patterns abuse exactly the kind of access stopSubscription 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 stopSubscription:
{
"version": "1",
"default": "deny",
"tools": {
"stopSubscription": {
"limits": [
{
"counter": "stopsubscription_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stopSubscription 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.
关闭指定订阅，释放 WebSocket 连接和缓冲区。已关闭的订阅 ID 不可复用。. 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 stopSubscription: 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.
stopSubscription 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 stopSubscription 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 stopSubscription. 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.
stopSubscription 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.