get_visit_history

Get past visit history and summaries

Server Teladoc MCP Server markswendsen-code/mcp-teladoc
Category Read
Risk class Low
Parameters 00 required

What get_visit_history does on Teladoc MCP Server

AI agents call get_visit_history 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.

Why get_visit_history needs a policy

This tool retrieves and queries historical healthcare visit data. It performs a read-only operation that returns information without creating, modifying, deleting, or executing any actions.

From the tool's definition Tool name is 'get_visit_history' and description states 'Get past visit history and summaries' — both indicate data retrieval with no modifications, deletions, or side effects.

Questions about get_visit_history

What does the get_visit_history tool do? +

Get past visit history and summaries. It is categorised as a Read tool in the Teladoc MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_visit_history? +

Register the Teladoc MCP Server MCP server in PolicyLayer and add a rule for get_visit_history: 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.

What risk level is get_visit_history? +

get_visit_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_visit_history? +

Yes. Add a rate_limit block to the get_visit_history 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.

How do I block get_visit_history completely? +

Set action: deny in the PolicyLayer policy for get_visit_history. 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.

What MCP server provides get_visit_history? +

get_visit_history 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.