get_uid_wallet_type

Get UID wallet type (UTA or classic).

SERVERBybit SOURCEjohnnywic/bybit-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/get-uid-wallet-type.md

WHAT IT DOES

What get_uid_wallet_type does on Bybit

AI agents call get_uid_wallet_type 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.

RISK

Why get_uid_wallet_type is rated Low

This tool retrieves read-only information about a user's wallet type classification. It has no side effects, does not execute trades, does not move funds, and does not modify any state. It is a simple informational query analogous to 'get' or 'fetch' operations.

From the tool's definition Tool name 'get_uid_wallet_type' and description 'Get UID wallet type (UTA or classic)' indicate a retrieval operation that queries account wallet configuration without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_uid_wallet_type Allowed

get_uid_wallet_type is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_uid_wallet_type": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_uid_wallet_type

What does the get_uid_wallet_type tool do? +

Get UID wallet type (UTA or classic). It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_uid_wallet_type? +

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

get_uid_wallet_type is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_uid_wallet_type? +

Yes. Add a rate_limit block to the get_uid_wallet_type 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 get_uid_wallet_type completely? +

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

get_uid_wallet_type 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →