Get structured discharge medication list for a patient.
AI agents call get_discharge_medications 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 queries and retrieves patient medication information from the discharge workflow without altering, deleting, or executing any operations. It is purely a read operation that fetches structured data for clinical review. While it does access PHI (protected health information), the server description indicates PHI boundary enforcement is in place.
From the tool's definition Tool name and description indicate retrieval of existing discharge medication data: 'Get structured discharge medication list for a patient.' No modification, deletion, or execution of commands occurs.
Attacks that exploit this kind of access
Get structured discharge medication list 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_discharge_medications: 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_discharge_medications 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_discharge_medications 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_discharge_medications. 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_discharge_medications 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 →