List upcoming and past Teladoc appointments
AI agents call list_appointments to retrieve information from Teladoc MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval operation that queries appointment data. While it accesses sensitive healthcare information (appointments are personal medical records), it performs no write, execute, or destructive actions. Classified as Read with medium severity due to the sensitive nature of healthcare data exposed (PHI/PII risk if misused), but the tool itself only retrieves without modifying state.
From the tool's definition Tool name 'list_appointments' and description 'List upcoming and past Teladoc appointments' indicate data retrieval with no modification or deletion. Returns appointment records without side effects.
Attacks that exploit this kind of access
List upcoming and past Teladoc appointments. It is categorised as a Read tool in the Teladoc MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Teladoc MCP Server MCP server in PolicyLayer and add a rule for list_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 Teladoc MCP Server. Nothing to install.
list_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 list_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 list_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.
list_appointments is provided by the Teladoc MCP Server MCP server (markswendsen-code/mcp-teladoc). 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 →