AI agents call list_classes to retrieve information from Mindbody without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_classes retrieves and queries class schedule data without side effects. This is a canonical Read operation: it gathers information to support decision-making but does not create, modify, delete, or execute actions. The blast radius of misuse is minimal—an agent might retrieve irrelevant class data or overwhelm the API, but cannot corrupt data or trigger payments.
From the tool's definition Tool description states 'Query class schedules and active class lists' — a retrieval operation with no modification, deletion, or execution of external processes. It surfaces existing data to inform scheduling decisions.
Attacks that exploit this kind of access
Query class schedules and active class lists within a date range. Used by AI scheduling agents to surface available classes to a caller. It is categorised as a Read tool in the Mindbody MCP Server, which means it retrieves data without modifying state.
Register the Mindbody MCP server in PolicyLayer and add a rule for list_classes: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mindbody. Nothing to install.
list_classes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_classes rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_classes. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_classes is provided by the Mindbody MCP server (nobanks/mindbody-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_classes is one line of Mindbody's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →