// SCAN REPORT

Mindbody

5 tools. 2 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 03/07/2026

How to control Mindbody ↓

TOOL MAP

What Mindbody exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mindbody tools

Financial · Critical checkout_shopping_cart This tool directly processes real financial transactions by charging clients for passes, services, or products. Write · High book_appointment This tool creates a new appointment booking, which is a reversible write operation (appointments can typically be cancelled).

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

POLICY

How to control Mindbody

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

Block financial tools by default

{
  "checkout_shopping_cart": {
    "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

{
  "book_appointment": {
    "limits": [
      {
        "counter": "book_appointment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "book_client_to_class": {
    "limits": [
      {
        "counter": "book_client_to_class_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register Mindbody — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MINDBODY →

Instant setup, no code required.

FULL CATALOGUE

All 5 Mindbody tools

FINANCIAL 1 tools

Financial checkout_shopping_cart Process purchases and complete payment checkout for passes, services, or products. GATED behind MINDBODY_ALLOW

WRITE 1 tools

Write book_appointment Schedule a single wellness or training appointment for a client with a specific staff member at a specific tim

READ 3 tools

Read book_client_to_class Enroll a client into an upcoming studio class. GATED behind MINDBODY_ALLOW_BOOKINGS env var. Returns an error Read get_client_info Fetch detailed profile information for a Mindbody client. Used by AI front-desk agents to ground responses in Read list_classes Query class schedules and active class lists within a date range. Used by AI scheduling agents to surface avai

FAQ

Questions about Mindbody

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

Yes. The Mindbody server exposes 1 financial tools including checkout_shopping_cart. 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 Mindbody? +

The Mindbody server has 1 write tools including book_appointment. 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 Mindbody.

How many tools does the Mindbody MCP server expose? +

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

How do I enforce a policy on Mindbody? +

Register the Mindbody 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 Mindbody tool call.

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

ENFORCE POLICY ON MINDBODY →

Instant setup, no code required.

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