23 tools. 5 can modify or destroy data without limits.
5 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (zenoti-appointments-progress, zenoti-feedback-submit, zenoti-guests-create) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
zenoti-appointments-progress:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
zenoti-appointments-checkin:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Zenoti server has 5 write tools including zenoti-appointments-progress, zenoti-feedback-submit, zenoti-guests-create. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
23 tools across 2 categories: Read, Write. 18 are read-only. 5 can modify, create, or delete data.
One line change. Instead of running the Zenoti server directly, prefix it with Intercept: intercept -c com-jamesrosingmd-zenoti.yaml -- npx -y @zenoti-mcp-server. Download a pre-built policy from policylayer.com/policies/com-jamesrosingmd-zenoti and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.