Menami

7 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

4 can modify or destroy data
3 read-only
7 tools total

Community server · catalogue entry verified 02/07/2026

How to control Menami ↓

What Menami exposes to your agents

Read (3) Write / Execute (3) Destructive / Financial (1)
Critical Risk

The most dangerous Menami tools

4 of Menami's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Menami

PolicyLayer is an MCP gateway — it sits between your AI agents and Menami, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "menami_place_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations
{
  "menami_book_table": {
    "limits": [
      {
        "counter": "menami_book_table_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "menami_consult_agent": {
    "limits": [
      {
        "counter": "menami_consult_agent_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Menami — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON MENAMI →

Instant setup, no code required.

All 7 Menami tools

Questions about Menami

Can an AI agent move money through the Menami MCP server? +

Yes. The Menami server exposes 1 financial tools including menami_place_order. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Menami? +

The Menami server has 3 write tools including menami_book_table, menami_manage_occasions, menami_submit_feedback. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Menami.

How many tools does the Menami MCP server expose? +

7 tools across 2 categories: Read, Write. 3 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Menami? +

Register the Menami MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Menami tool call.

Deterministic rules across all 7 Menami tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

7 Menami tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.