Get past prescriptions and diagnosis history for a patient.
AI agents call get_patient_history to retrieve information from MCPDischarge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical medical data (prescriptions and diagnoses) without side effects. It is a Read operation. Severity is elevated to medium rather than low because the data accessed is PHI (Protected Health Information) in a healthcare context; unauthorized or incorrect retrieval of a patient's medical history could lead to care errors, privacy breaches, or misuse of sensitive information.
From the tool's definition Tool name 'get_patient_history' and description 'Get past prescriptions and diagnosis history for a patient' indicate data retrieval with no modification. The verb 'Get' and absence of terms like 'modify', 'delete', or 'execute' confirm read-only behavior.
Attacks that exploit this kind of access
Get past prescriptions and diagnosis history for a patient. It is categorised as a Read tool in the MCPDischarge MCP Server, which means it retrieves data without modifying state.
Register the MCPDischarge MCP server in PolicyLayer and add a rule for get_patient_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 MCPDischarge. Nothing to install.
get_patient_history 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_patient_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.
Set action: deny in the PolicyLayer policy for get_patient_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.
get_patient_history is provided by the MCPDischarge MCP server (prashantsingh1234/mcp_project). 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 →