create_appointment · Cliniko MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_appointment does on Cliniko MCP Server

AI agents use create_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 create_appointment needs a policy

The tool creates new appointment data in a healthcare practice management system. This is a Write operation (reversible modification) rather than Execute because it does not trigger external operations or run arbitrary code—it simply creates a structured record. Severity is medium because incorrect appointment creation could disrupt scheduling and patient care but can be undone.

From the tool's definition Tool name 'create_appointment' indicates data creation. Server context shows this is a practice management system handling patient appointments. The tool creates new appointment records which are reversible via delete_appointment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_appointment Rate-limited

create_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": {
    "create_appointment": {
      "limits": [
        {
          "counter": "create_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 create_appointment

What does the create_appointment tool do? +

create_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 create_appointment? +

Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for create_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 create_appointment? +

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

Can I rate-limit create_appointment? +

Yes. Add a rate_limit block to the create_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 create_appointment completely? +

Set action: deny in the PolicyLayer policy for create_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 create_appointment? +

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