Get all encounters for a patient
AI agents call get_patient_encounters to retrieve information from athenahealth 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 healthcare encounter data for a patient without creating, modifying, or deleting information. While it is a Read operation and thus lower severity than Write/Execute/Destructive categories, the severity is elevated to 'high' due to access to sensitive Protected Health Information (PHI) under HIPAA. Misuse by an AI agent could expose comprehensive patient medical history and encounter details.
From the tool's definition Tool name 'get_patient_encounters' and description 'Get all encounters for a patient' indicate retrieval of data without modification. The action is a read operation that queries patient encounter records.
Attacks that exploit this kind of access
Get all encounters for a patient. It is categorised as a Read tool in the athenahealth MCP Server MCP Server, which means it retrieves data without modifying state.
Register the athenahealth MCP Server MCP server in PolicyLayer and add a rule for get_patient_encounters: 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 athenahealth MCP Server. Nothing to install.
get_patient_encounters 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_encounters 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_encounters. 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_encounters is provided by the athenahealth MCP Server MCP server (ophydami/athenahealth-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 →