# menese_lend

[Coming soon] Supply or withdraw assets on Aave V3 (EVM chains).

Agent View of the PolicyLayer registry record for `menese_lend`. HTML page: https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-lend

## Facts

- Tool: `menese_lend`
- Server: Mcp Menesesdk (`aboodtt404/mcp-menese-sdk`) — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk.md
- Homepage: https://github.com/Aboodtt404/mcp-menese-sdk
- Risk category: Financial (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "menese_lend",
    "arguments": {}
  }
}
```

## Why menese_lend is rated Critical

Supplying or withdrawing assets on Aave V3 involves real financial operations: locking tokens as collateral or retrieving funds from a lending protocol. Even though the tool is marked '[Coming soon]', its described functionality is clearly Financial in nature — committing or reclaiming assets with real monetary value.

From the tool's own definition: "'Supply or withdraw assets on Aave V3' — this tool moves crypto assets into/out of a DeFi lending protocol, constituting financial transactions."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Menesesdk:

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

## Other tools on Mcp Menesesdk (10)

- `menese_jobs` — Execute — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-jobs.md
- `menese_send` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-send.md
- `menese_stake` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-stake.md
- `menese_swap` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-swap.md
- `menese_balance` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-balance.md
- `menese_portfolio` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-portfolio.md
- `menese_prices` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-prices.md
- `menese_quote` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-quote.md
- `menese_setup` — Write — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-setup.md
- `menese_strategy` — Write — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-strategy.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aboodtt404-mcp-menese-sdk · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aboodtt404-mcp-menese-sdk