Borrow an asset from the Kaskad Protocol lending pool. Requires sufficient collateral.
AI agents use borrow 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.
Borrowing from a DeFi lending pool is a financial operation that creates an on-chain debt obligation. Misuse by an AI agent could result in unauthorized debt positions, exposure to liquidation, and financial loss. This is the most severe category applicable.
From the tool's definition 'Borrow an asset from the Kaskad Protocol lending pool' — directly borrows assets (creates financial obligation) from a DeFi lending protocol, committing the user to a debt position that incurs interest and liquidation risk
Attacks that exploit this kind of access
Borrow an asset from the Kaskad Protocol lending pool. Requires sufficient collateral. 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 borrow: 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.
borrow 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 borrow 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 borrow. 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.
borrow 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 →