setDefaultDepositToAccount
Set the default account type for receiving on-chain deposit funds.\n- Only main UID API key can call this endpoint\n- Sub-accounts are not allowed\n- Funds default to
This record as markdown: /tools/bybit-exchange-trading-mcp/setdefaultdeposittoaccount.md
What setDefaultDepositToAccount does on Bybit MCP Server
AI agents use setDefaultDepositToAccount 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.
Why setDefaultDepositToAccount is rated Medium
This tool modifies account configuration (default deposit destination) which is a reversible write operation. It doesn't move funds directly but changes where future deposits are routed, which could have significant financial implications if misconfigured. Severity is medium because it affects fund routing but doesn't directly move money or delete data.
From the tool's definition Set the default account type for receiving on-chain deposit funds
Attacks that exploit this kind of access
The rule that runs setDefaultDepositToAccount safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setDefaultDepositToAccount, this is the rule to start with:
setDefaultDepositToAccount 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every setDefaultDepositToAccount call is checked against it from then on.
Questions about setDefaultDepositToAccount
Set the default account type for receiving on-chain deposit funds.\n- Only main UID API key can call this endpoint\n- Sub-accounts are not allowed\n- Funds default to. 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 setDefaultDepositToAccount: 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.
setDefaultDepositToAccount 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 setDefaultDepositToAccount 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 setDefaultDepositToAccount. 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.
setDefaultDepositToAccount 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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue