List whitelisted withdrawal addresses.
AI agents call get_withdrawal_addresses to retrieve information from Mcp Kraken without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account configuration data (whitelisted addresses) for informational purposes only. It performs no write, destructive, financial transaction, or code execution. The read operation has minimal blast radius—an attacker learning withdrawal addresses cannot directly transfer funds or cause financial loss without additional tools like account_transfer or add_order.
From the tool's definition Tool name 'get_withdrawal_addresses' and description 'List whitelisted withdrawal addresses' indicate a query operation that retrieves existing data without modification or execution of transactions.
Attacks that exploit this kind of access
List whitelisted withdrawal addresses. It is categorised as a Read tool in the Mcp Kraken MCP Server, which means it retrieves data without modifying state.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for get_withdrawal_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 Mcp Kraken. Nothing to install.
get_withdrawal_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_withdrawal_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_withdrawal_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_withdrawal_addresses is provided by the Mcp Kraken MCP server (xavierbeheydt/mcp-kraken). 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 →