Configure the time window for automatic order cancellation when WebSocket connection drops.\n\n- Institutional users only; must be enabled via account manager\n- Supports options, derivatives (futures), and spot products\n- Time window range: 3-300 seconds\n- After setting, activate DCP stream on...
AI agents use setDcp 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 writes/modifies a configuration setting that controls automatic order cancellation behavior. While it doesn't directly cancel orders itself, it configures a safety mechanism that will automatically cancel ALL orders across specified product types when triggered. Misuse could lead to unintended mass order cancellations or, conversely, disabling a safety mechanism — making severity high.
From the tool's definition Configure the time window for automatic order cancellation when WebSocket connection drops
Documented attack patterns abuse exactly the kind of access setDcp 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 setDcp:
{
"version": "1",
"default": "deny",
"tools": {
"setDcp": {
"limits": [
{
"counter": "setdcp_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setDcp 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.
Configure the time window for automatic order cancellation when WebSocket connection drops.\n\n- Institutional users only; must be enabled via account manager\n- Supports options, derivatives (futures), and spot products\n- Time window range: 3-300 seconds\n- After setting, activate DCP stream on private WebSocket to enable triggering\n- Allow ~10 seconds for system propagation\n\nAgent hint: Use this endpoint to set the DCP time window. When WebSocket disconnects for longer than this window, all orders for the specified product are automatically cancelled. 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 setDcp: 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.
setDcp 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 setDcp 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 setDcp. 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.
setDcp 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.