取得目前登入帳戶的用戶資訊（KYC 狀態、帳號 ID 等）
AI agents call get_user_info to retrieve information from MAX Exchange MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries account metadata without modifying or deleting data, placing it in the Read category. Severity is medium rather than low because the exposed information (KYC status, account ID) could be sensitive personal/financial identifiers useful for account takeover, social engineering, or identity fraud if an AI agent exfiltrates this data to an attacker.
From the tool's definition Tool retrieves user account information including KYC status and account ID. Description states 'get' (retrieve) with no modification or deletion semantics. The name 'get_user_info' and function signature confirm read-only data retrieval.
Attacks that exploit this kind of access
取得目前登入帳戶的用戶資訊（KYC 狀態、帳號 ID 等）. It is categorised as a Read tool in the MAX Exchange MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MAX Exchange MCP Server MCP server in PolicyLayer and add a rule for get_user_info: 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 MAX Exchange MCP Server. Nothing to install.
get_user_info 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_user_info 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_user_info. 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_user_info is provided by the MAX Exchange MCP Server MCP server (nicky512500/max-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 →