get_deposit_addresses
AI agents call get_deposit_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.
Retrieving deposit addresses is a read-only operation that queries account data without side effects. While deposit addresses are sensitive information, the tool itself does not execute code, modify data, delete data, or move funds. The empty description reduces confidence slightly, but the name and context clearly indicate a data retrieval function typical of exchange account queries.
From the tool's definition Tool name 'get_deposit_addresses' indicates retrieval of deposit address data with no modification or financial transaction. The Kraken API context shows this is a query-only operation that returns cryptocurrency deposit addresses associated with the account.
Attacks that exploit this kind of access
get_deposit_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_deposit_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_deposit_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_deposit_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_deposit_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_deposit_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 →