create_practitioner
AI agents use create_practitioner 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.
Creating a practitioner record in a medical practice management system modifies the system state by adding a new staff member or provider. This is reversible (practitioners can be deleted, as evidenced by the sibling tool 'delete_practitioner'), so it falls under Write rather than Destructive.
From the tool's definition Tool name is 'create_practitioner' which indicates creation of a new practitioner record. The server description confirms this is a practice management system supporting 'patient management' and 'practice data access', making practitioner creation a data…
Attacks that exploit this kind of access
create_practitioner. 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.
Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for create_practitioner: 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.
create_practitioner is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_practitioner 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 create_practitioner. 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.
create_practitioner 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 →