get_patient
AI agents call get_patient 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 patient data from the Cliniko practice management system with no modifications. While patient data is sensitive (medical information), the tool itself performs read-only access with no destructive or state-changing capability. Severity is low because exposure depends on API authentication and data sensitivity policies already in place at the healthcare provider level.
From the tool's definition Tool name is 'get_patient' which follows the standard 'get_*' pattern indicating data retrieval. Server context describes 'patient management' and 'practice data access' as core functions.
Attacks that exploit this kind of access
get_patient. 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 get_patient: 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.
get_patient 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 get_patient 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 get_patient. 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.
get_patient 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 →