AI agents call get_asset_sub_uid_list to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of sub UIDs for asset transfers. It performs no state changes, does not execute commands, does not delete data, and does not move money. It is a straightforward data retrieval operation. On a trading exchange platform, knowing available sub UIDs is low-risk information that supports account management but poses minimal security risk if misused by an AI agent.
From the tool's definition Tool name 'get_asset_sub_uid_list' and description 'Get sub UID list for asset transfers' indicate a query/retrieval operation. The word 'get' and 'list' are characteristic of read-only operations that retrieve data without modification.
Attacks that exploit this kind of access
Get sub UID list for asset transfers. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_asset_sub_uid_list: 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.
get_asset_sub_uid_list 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 get_asset_sub_uid_list 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 get_asset_sub_uid_list. 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.
get_asset_sub_uid_list 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →