取得提現歷史記錄
AI agents call get_withdrawals 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 withdrawal history records from a cryptocurrency exchange, which is a data query operation with no side effects. It falls under the Read category as it only fetches existing data. Severity is medium rather than low because the retrieved data reveals financial transaction history and account activity patterns that could be sensitive; however, the tool itself causes no direct harm or financial loss.
From the tool's definition Tool name 'get_withdrawals' and description '取得提現歷史記錄' (retrieve withdrawal history records) indicate querying/retrieving historical data with no modification of state.
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_withdrawals: 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_withdrawals 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_withdrawals 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_withdrawals. 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_withdrawals 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 →