AI agents call get_client_info 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.
This tool retrieves and queries existing client profile data without creating, modifying, deleting, or executing any operations. It is a straightforward Read operation. Severity is low because while client information may be sensitive (privacy concern), the tool itself has no destructive, financial, or execution capabilities—it simply returns data. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'get_client_info' and description 'Fetch detailed profile information' indicate data retrieval. The phrase 'Used by AI front-desk agents to ground responses in customer history' confirms this is informational lookup with no side effects.
Attacks that exploit this kind of access
Fetch detailed profile information for a Mindbody client. Used by AI front-desk agents to ground responses in customer history. 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 get_client_info: 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.
get_client_info 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 get_client_info 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 get_client_info. 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.
get_client_info 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →