# menese_stake

[Coming soon] Stake ETH via Lido protocol on EVM chains.

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

## Facts

- Tool: `menese_stake`
- 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_stake",
    "arguments": {}
  }
}
```

## Why menese_stake is rated Critical

Staking ETH is a financial operation that locks/commits cryptocurrency assets. Even though the description says 'Coming soon', the intent is to stake ETH via Lido, which is a financial commitment of real assets on EVM chains. Misuse could result in unintended locking of user funds. Severity is critical due to the irreversible nature of staking and potential financial loss.

From the tool's own definition: "Stake ETH via Lido protocol on EVM chains"

## Use case

AI agents use menese_stake 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_stake": {
      "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_lend` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-lend.md
- `menese_send` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-send.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