取得平台內部轉帳記錄（MAX 用戶間互轉）
AI agents call get_internal_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 existing transaction records between MAX Exchange users. It is a read-only operation that does not create, modify, delete, or execute any actions—it only fetches historical data. Even in the context of a financial platform, the tool itself performs no financial operation; it merely returns information about past transfers.
From the tool's definition Tool name 'get_internal_transfers' and description '取得平台內部轉帳記錄（MAX 用戶間互轉）' (Get internal transfer records - transfers between MAX users) indicate retrieval of historical transfer data with no modification capability.
Attacks that exploit this kind of access
取得平台內部轉帳記錄（MAX 用戶間互轉）. 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_internal_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_internal_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_internal_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_internal_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_internal_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 →