Get patient
AI agents call get_appointments to retrieve information from Agent Care MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves appointment information for a patient from an EMR system (Cerner/Epic via FHIR). It has no side effects—it only reads data. However, severity is 'high' rather than 'low' because unauthorized access to patient appointment data constitutes a HIPAA violation and could enable privacy breaches, stalking, or other harms, even though the operation itself is non-destructive.
From the tool's definition Tool name 'get_appointments' and description 'Get patient' indicate data retrieval operations. Sibling tools (find_patient, get_lab_results, get_medications_history, get_patient_allergies, etc.) are all Read operations that retrieve patient data without…
Attacks that exploit this kind of access
Get patient. It is categorised as a Read tool in the Agent Care MCP MCP Server, which means it retrieves data without modifying state.
Register the Agent Care MCP server in PolicyLayer and add a rule for get_appointments: 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 Agent Care MCP. Nothing to install.
get_appointments 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_appointments 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_appointments. 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_appointments is provided by the Agent Care MCP server (polya20/agentcare-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_appointments is one line of Agent Care's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →