Get details of a specific encounter
AI agents call get_encounter 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 encounter information from a healthcare system. While it is a Read operation (no modifications), the severity is high because encounters contain sensitive protected health information (PHI) including diagnoses, treatments, and clinical notes.
From the tool's definition Tool name is 'get_encounter' with description 'Get details of a specific encounter' — uses 'get' and 'details' indicating data retrieval with no side effects.
Attacks that exploit this kind of access
Get details of a specific encounter. 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_encounter: 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_encounter 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_encounter 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_encounter. 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_encounter 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 →