取得單筆 M 錢包清算詳情
AI agents call get_m_liquidation 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 historical or current liquidation details from an M-wallet (lending wallet) without creating, modifying, or triggering new financial transactions. It is a read-only query operation. While the broader server context involves financial operations, this specific tool only accesses data rather than executing financial movements or trade execution.
From the tool's definition Tool name contains 'get_' prefix and description '取得單筆 M 錢包清算詳情' (Chinese: 'Get single M wallet liquidation details') indicates retrieval of existing liquidation information without modification or execution of trades.
Attacks that exploit this kind of access
取得單筆 M 錢包清算詳情. 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_m_liquidation: 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_m_liquidation 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_m_liquidation 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_m_liquidation. 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_m_liquidation 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 →