Low Risk

getMemberAccountType

Get account type information for specified member IDs. Use master or sub-account

How to control getMemberAccountType ↓

What getMemberAccountType does on Bybit MCP Server

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

Low Risk

Why getMemberAccountType needs a policy

This tool queries and retrieves account type information without modifying, deleting, or executing any actions. However, it accesses sensitive financial account data on a cryptocurrency exchange, which elevates severity to medium despite being Read category.

From the tool's definition Tool description states 'Get account type information for specified member IDs' — a retrieval operation with no side effects. The verb 'Get' explicitly indicates read-only access to account metadata.

Documented attack patterns abuse exactly the kind of access getMemberAccountType gives an agent:

How to control getMemberAccountType

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 getMemberAccountType:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getMemberAccountType": {}
  }
}

getMemberAccountType is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Bybit MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getMemberAccountType

What does the getMemberAccountType tool do? +

Get account type information for specified member IDs. Use master or sub-account. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getMemberAccountType? +

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

What risk level is getMemberAccountType? +

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

Can I rate-limit getMemberAccountType? +

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

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

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

Enforce policy on every Bybit MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.