Preview withdrawal cost (fee, limits).
AI agents call get_withdrawal_info 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 merely retrieves and displays withdrawal-related metadata (fees and limits) for informational purposes. It has no side effects, does not execute transactions, does not modify account state, and does not move funds. It is a straightforward data lookup operation, fitting the 'Read' category. The context of a cryptocurrency exchange does not elevate risk when the specific operation is informational only.
From the tool's definition Tool name 'get_withdrawal_info' and description 'Preview withdrawal cost (fee, limits)' indicate a read-only query operation that retrieves fee and limit information without executing or modifying any state.
Attacks that exploit this kind of access
Preview withdrawal cost (fee, limits). 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_info: 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_info 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_info 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_info. 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_info 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 →