get_dcp_info
Get Disconnect Cancel All (DCP) configuration info.
This record as markdown: /tools/johnnywic-bybit-mcp/get-dcp-info.md
What get_dcp_info does on Bybit
AI agents call get_dcp_info to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dcp_info is rated Low
This is a straightforward read operation that retrieves configuration information about DCP settings. The 'get' verb and passive description confirm it performs query/fetch semantics without any capability to modify state, execute code, or trigger trading operations.
From the tool's definition Tool name 'get_dcp_info' with verb 'get' and description 'Get Disconnect Cancel All (DCP) configuration info' indicates data retrieval with no side effects. It queries configuration settings without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_dcp_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dcp_info, this is the rule to start with:
get_dcp_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every get_dcp_info call is checked against it from then on.
Questions about get_dcp_info
Get Disconnect Cancel All (DCP) configuration info. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_dcp_info: 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.
get_dcp_info 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 get_dcp_info 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 get_dcp_info. 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.
get_dcp_info 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue