update_appointment · Cliniko MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_appointment does on Cliniko MCP Server

AI agents use update_appointment to create or update resources in Cliniko MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cliniko MCP Server environment.

WHY IT NEEDS A POLICY

Why update_appointment needs a policy

The tool modifies existing appointment records reversibly (updates rather than deletes). This is a Write operation—it changes data but does not irreversibly destroy it or move money. In a healthcare context, updating appointments affects scheduling and patient care coordination, justifying medium severity.

From the tool's definition Tool name 'update_appointment' indicates modification of appointment data. Sibling tools include destructive operations (delete_*) and financial operations (create_invoice), confirming this is a healthcare practice management system where data modifications…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_appointment Rate-limited

update_appointment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_appointment": {
      "limits": [
        {
          "counter": "update_appointment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cliniko MCP Server, so you can run agents against it safely.

FAQ

Questions about update_appointment

What does the update_appointment tool do? +

update_appointment. It is categorised as a Write tool in the Cliniko MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_appointment? +

Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_appointment? +

update_appointment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_appointment? +

Yes. Add a rate_limit block to the update_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.

How do I block update_appointment completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_appointment? +

update_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.