Query Disconnection Protection (DCP) configuration. Returns DCP status and\ntime window per product type. Must be pre-authorized by account manager.\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check DCP settings. No parameters needed. Returns an array of\nproduct-level DCP configs with sta...
AI agents call getDcpInfo to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account configuration information without side effects. It queries read-only DCP settings that are pre-configured by account managers. No data is created, modified, deleted, or financial transactions are triggered. The severity is low because disclosure of DCP configuration poses minimal risk—DCP is a protective feature and its configuration is not operationally sensitive.
From the tool's definition Tool description states: "Query Disconnection Protection (DCP) configuration" and "Returns DCP status and time window per product type". The verb "Query" and "Returns" indicate data retrieval.
Documented attack patterns abuse exactly the kind of access getDcpInfo 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 getDcpInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getDcpInfo": {}
}
}getDcpInfo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query Disconnection Protection (DCP) configuration. Returns DCP status and\ntime window per product type. Must be pre-authorized by account manager.\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check DCP settings. No parameters needed. Returns an array of\nproduct-level DCP configs with status and time window. Only works for accounts\nthat have DCP enabled by their account manager. Empty result means DCP is not configured. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getDcpInfo: 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.
getDcpInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getDcpInfo 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 getDcpInfo. 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.
getDcpInfo 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.