Withdraw a supplied asset from the Kaskad Protocol lending pool. Pass amount=-1 to withdraw all. Testnet only.
AI agents use withdraw to commit financial operations through Kaskad Protocol MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves assets (cryptocurrency/tokens) from a user's position in a DeFi lending protocol, constituting a financial transaction. Misuse by an AI agent could result in unauthorized withdrawal of user funds, causing direct monetary loss. While classified as testnet-only, the core functionality commits financial obligations and transfers value, making it Financial rather than Write.
From the tool's definition Tool description states 'Withdraw a supplied asset from the Kaskad Protocol lending pool' and server description indicates 'full write access' to a 'DeFi lending protocol' that handles financial operations including 'supply, borrow, repay, withdraw, and stake.
Attacks that exploit this kind of access
Withdraw a supplied asset from the Kaskad Protocol lending pool. Pass amount=-1 to withdraw all. Testnet only. It is categorised as a Financial tool in the Kaskad Protocol MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Kaskad Protocol MCP Server MCP server in PolicyLayer and add a rule for withdraw: 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 Kaskad Protocol MCP Server. Nothing to install.
withdraw is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the withdraw 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 withdraw. 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.
withdraw is provided by the Kaskad Protocol MCP Server MCP server (kaskad-lending/kaskad-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 →