aave_withdraw

Withdraws a bounded ERC-20 amount from Base Aave V3 to the Agent wallet or a specified recipient.

SERVERAwesome Base SOURCEB5-Software/awesome-base-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/awesome-base-mcp/aave-withdraw.md

WHAT IT DOES

What aave_withdraw does on Awesome Base

AI agents use aave_withdraw to commit financial operations through Awesome Base, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why aave_withdraw is rated Critical

Moves crypto assets from Aave lending protocol to a wallet, committing a financial transaction.

From the tool's definition Withdraws a bounded ERC-20 amount from Base Aave V3

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs aave_withdraw safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Awesome Base, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aave_withdraw, this is the rule to start with:

aave_withdraw Approval-gated

Any call to aave_withdraw is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aave_withdraw": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Awesome Base, apply this rule, and every aave_withdraw call is checked against it from then on.

FAQ

Questions about aave_withdraw

What does the aave_withdraw tool do? +

Withdraws a bounded ERC-20 amount from Base Aave V3 to the Agent wallet or a specified recipient. It is categorised as a Financial tool in the Awesome Base MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on aave_withdraw? +

Register the Awesome Base MCP server in PolicyLayer and add a rule for aave_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 Awesome Base. Nothing to install.

What risk level is aave_withdraw? +

aave_withdraw is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit aave_withdraw? +

Yes. Add a rate_limit block to the aave_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.

How do I block aave_withdraw completely? +

Set action: deny in the PolicyLayer policy for aave_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.

What MCP server provides aave_withdraw? +

aave_withdraw is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Awesome Base, and thousands of servers like it.

This server

All 44 Awesome Base tools → Critical-risk tools on this server →

Across the catalogue

build_redeem_withdraw_tx on Atv → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →