getMemberAccountType
Get account type information for specified member IDs. Use master or sub-account
This record as markdown: /tools/bybit-exchange-trading-mcp/getmemberaccounttype.md
What getMemberAccountType does on Bybit MCP Server
AI agents call getMemberAccountType to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getMemberAccountType is rated Low
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.
Attacks that exploit this kind of access
The rule that runs getMemberAccountType 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 getMemberAccountType, this is the rule to start with:
getMemberAccountType 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 MCP Server, apply this rule, and every getMemberAccountType call is checked against it from then on.
Questions about getMemberAccountType
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.
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.
getMemberAccountType 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 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.
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.
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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue