# menese_setup

Create or import a Menese wallet. Actions:

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

## Facts

- Tool: `menese_setup`
- 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: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why menese_setup is rated Medium

The tool creates new wallets or imports existing ones, which are reversible data modifications (wallets can be recreated or deleted). While it operates in a financial context (DeFi gateway), it does not itself move money or commit financial obligations—it only sets up the account infrastructure. This places it in Write rather than Financial.

From the tool's own definition: "Tool description states 'Create or import a Menese wallet' — both create and import are write operations that establish or modify wallet state."

## Use case

AI agents use menese_setup to create or update resources in Mcp Menesesdk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Menesesdk environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "menese_setup": {
      "limits": [
        {
          "counter": "menese_setup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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_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_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