Get prescription history from Teladoc
AI agents call get_prescriptions 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 tool retrieves historical prescription data without creating, modifying, or deleting records. It is a read-only query operation. Severity is medium rather than low due to the sensitive health information accessed (prescription history), which could pose privacy/confidentiality risks if misused by an agent, but has no direct operational impact on system state or medical care delivery.
From the tool's definition Tool name 'get_prescriptions' and description 'Get prescription history from Teladoc' indicate a data retrieval operation with no modification or destructive capability.
Attacks that exploit this kind of access
Get prescription history from Teladoc. 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 get_prescriptions: 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.
get_prescriptions 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_prescriptions 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_prescriptions. 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_prescriptions 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 →