list_practitioners
AI agents call list_practitioners 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.
This tool retrieves practitioner data from the Cliniko practice management system without side effects. Listing practitioner records is a query operation. While the description is empty, the tool name 'list_practitioners' clearly indicates data retrieval. The severity is low because exposure of practitioner roster information, though sensitive, is typically less critical than patient data or financial transactions.
From the tool's definition Tool name 'list_practitioners' indicates retrieval/enumeration of practitioner records. No parameters or effects described that suggest modification or deletion. The 'list' verb is characteristic of Read category tools.
Attacks that exploit this kind of access
list_practitioners. 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_practitioners: 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_practitioners 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_practitioners 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_practitioners. 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_practitioners 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 →