list_patients
AI agents call list_patients 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 'list' prefix is a strong indicator of a Read operation—it retrieves or enumerates data with no side effects. In a medical practice management system (Cliniko), listing patients would fetch existing records for display or querying purposes without creating, modifying, or deleting anything. This is the least severe category.
From the tool's definition Tool name 'list_patients' indicates a listing operation that queries and retrieves patient data without modification. The server context (patient management system) and sibling tools (create_*, delete_*, get_*) suggest this performs data retrieval.
Attacks that exploit this kind of access
list_patients. 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_patients: 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_patients 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_patients 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_patients. 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_patients 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 →