get_appointment
AI agents call get_appointment 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 'get_' prefix strongly suggests a read-only query operation. The tool retrieves existing appointment information from the Cliniko system with no side effects. Although sensitive healthcare data may be involved, the operation itself is non-destructive and reversible, classifying it as Read rather than a higher severity category. Confidence is high but not maximal due to the empty description.
From the tool's definition Tool name 'get_appointment' indicates a retrieval operation. No description provided, but context from sibling tools (create_*, delete_*) and the server's stated purpose of 'appointment scheduling and practice data access' confirms this retrieves appointment…
Attacks that exploit this kind of access
get_appointment. 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 get_appointment: 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.
get_appointment 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_appointment 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_appointment. 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_appointment 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 →