取得 M 錢包資金轉移記錄
AI agents call get_m_transfers 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 and retrieves M-wallet transfer history. It has no side effects—it only reads and returns existing data about past fund transfers. No data is created, modified, deleted, or financial transactions are executed. This is a straightforward data retrieval operation, consistent with other Read category tools like get_accounts, get_deposits, and get_closed_orders on the same server.
From the tool's definition Tool name 'get_m_transfers' and description '取得 M 錢包資金轉移記錄' (Get M-wallet fund transfer records) indicate retrieval of historical transaction data with no modification or execution capabilities.
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_transfers: 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_transfers 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_transfers 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_transfers. 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_transfers 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 →