Get full patient discharge summary (PHI — restricted via RBAC).
AI agents call get_patient_discharge_summary 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 data without side effects, making it a Read operation. However, severity is elevated to 'high' because: (1) the retrieved data is PHI subject to HIPAA and similar regulations, (2) unauthorized access to discharge summaries could expose sensitive medical history, medications, diagnoses, and treatment plans, and (3) the explicit mention of RBAC enforcement suggests access control is critical to…
From the tool's definition Tool name uses 'Get' verb and description states 'Get full patient discharge summary'; retrieval operation with no modification, deletion, or execution indicated.
Attacks that exploit this kind of access
Get full patient discharge summary (PHI — restricted via RBAC). 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_discharge_summary: 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_discharge_summary 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_discharge_summary 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_discharge_summary. 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_discharge_summary 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 →