Search for patients by name, DOB, phone, or email
AI agents call search_patients 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 patient data based on search criteria without creating, modifying, or deleting records. It is a read operation. However, severity is high (not low/medium) because: (1) it operates on protected health information (PHI) under HIPAA, (2) successful unauthorized access could expose sensitive patient identities and contact details across potentially large result sets, (3) it could enable patient…
From the tool's definition Tool name 'search_patients' and description 'Search for patients by name, DOB, phone, or email' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Search for patients by name, DOB, phone, or email. 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 search_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 athenahealth MCP Server. Nothing to install.
search_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 search_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 search_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.
search_patients 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 →