取得已綁定的提現地址列表
AI agents call get_withdraw_addresses 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 retrieves previously configured withdrawal addresses from the user's account without creating, modifying, or deleting any data. While it relates to a financial account (MAX Exchange), it does not move money, commit financial obligations, or execute transactions—it merely queries and displays stored address information. The operation is informational only, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_withdraw_addresses' and description '取得已綁定的提現地址列表' (Get list of bound withdrawal addresses) indicate retrieval of existing address data. The verb 'get' and action of listing addresses are read-only operations with no side effects.
Attacks that exploit this kind of access
取得已綁定的提現地址列表. 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_withdraw_addresses: 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_withdraw_addresses 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_withdraw_addresses 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_withdraw_addresses. 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_withdraw_addresses 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 →