list_appointments
AI agents call list_appointments to retrieve information from Cliniko MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_appointments' tool performs a read-only query of appointment data. Although the description is empty, the name clearly indicates data retrieval (list) rather than creation, modification, or deletion. The sibling tools include destructive variants (delete_appointment, delete_invoice, delete_patient, delete_practitioner), but this tool is the corresponding read operation.
From the tool's definition Tool name 'list_appointments' indicates a listing/retrieval operation with no description provided. In the context of the Cliniko practice management server, listing operations are standard data retrieval functions.
Attacks that exploit this kind of access
list_appointments. It is categorised as a Read tool in the Cliniko MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for list_appointments: 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 Cliniko MCP Server. Nothing to install.
list_appointments 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_appointments 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_appointments. 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_appointments is provided by the Cliniko MCP Server MCP server (yasboop/new-cliniko-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 →