Withdraws tokens from Aave, redeeming your supplied assets (aTokens).
AI agents use intentAaveWithdraw to commit financial operations through Agentek Eth — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly withdraws cryptocurrency from a user's Aave position, which constitutes a financial transaction that moves money/crypto assets. The blast radius is critical because an AI agent with this capability could drain user funds from Aave without authorization. This takes precedence over Execute category because the tool's primary purpose is financial asset movement, not general code execution.
From the tool's definition Tool name 'intentAaveWithdraw' and description 'Withdraws tokens from Aave, redeeming your supplied assets' indicates movement of cryptocurrency assets from a lending protocol.
Documented attack patterns abuse exactly the kind of access intentAaveWithdraw gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentek Eth, and nothing reaches the server without passing your rules. This is the rule we recommend for intentAaveWithdraw:
{
"version": "1",
"default": "deny",
"tools": {
"intentAaveWithdraw": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to intentAaveWithdraw is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Withdraws tokens from Aave, redeeming your supplied assets (aTokens). It is categorised as a Financial tool in the Agentek Eth MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for intentAaveWithdraw: 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 Agentek Eth. Nothing to install.
intentAaveWithdraw 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 intentAaveWithdraw 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 intentAaveWithdraw. 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.
intentAaveWithdraw is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentek Eth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
165 Agentek Eth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.