freeze_sub_uid

Freeze or unfreeze a sub UID.

SERVERBybit SOURCEjohnnywic/bybit-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/freeze-sub-uid.md

WHAT IT DOES

What freeze_sub_uid does on Bybit

AI agents invoke freeze_sub_uid to trigger actions in Bybit. 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.

RISK

Why freeze_sub_uid is rated High

This tool modifies the operational state of a sub-account (UID) by freezing or unfreezing it, which is a significant account management action. Freezing a sub UID would prevent it from trading or accessing funds, making it an Execute-level operation with high blast radius since it can disrupt trading activity for an entire sub-account.

From the tool's definition Freeze or unfreeze a sub UID

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs freeze_sub_uid 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 freeze_sub_uid, this is the rule to start with:

freeze_sub_uid Rate-limited

freeze_sub_uid 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "freeze_sub_uid": {
      "limits": [
        {
          "counter": "freeze_sub_uid_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every freeze_sub_uid call is checked against it from then on.

FAQ

Questions about freeze_sub_uid

What does the freeze_sub_uid tool do? +

Freeze or unfreeze a sub UID. It is categorised as a Execute tool in the Bybit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on freeze_sub_uid? +

Register the Bybit MCP server in PolicyLayer and add a rule for freeze_sub_uid: 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.

What risk level is freeze_sub_uid? +

freeze_sub_uid is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit freeze_sub_uid? +

Yes. Add a rate_limit block to the freeze_sub_uid 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.

How do I block freeze_sub_uid completely? +

Set action: deny in the PolicyLayer policy for freeze_sub_uid. 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.

What MCP server provides freeze_sub_uid? +

freeze_sub_uid 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.

KEEP EXPLORING

More on Bybit, and thousands of servers like it.

This server

All 245 Bybit tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →