Add a new medication to patient records with proper validation and allergy checking
AI agents use addMedication to create or update resources in Medical MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Medical MCP Server environment.
This tool modifies patient medical records by adding new medications. While medication management is safety-critical in healthcare, the action itself is reversible (medications can be edited or discontinued), placing it in Write rather than Destructive. Severity is high because erroneous medication additions could impact patient care and safety, and the data involves sensitive protected health information (PHI).
From the tool's definition Tool description states it 'Add[s] a new medication to patient records' which creates new data entries. The tool performs data modification operations (adding medication records) that are reversible through other operations like editMedication or…
Attacks that exploit this kind of access
Add a new medication to patient records with proper validation and allergy checking. It is categorised as a Write tool in the Medical MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Medical MCP Server MCP server in PolicyLayer and add a rule for addMedication: 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 Medical MCP Server. Nothing to install.
addMedication is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the addMedication 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 addMedication. 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.
addMedication is provided by the Medical MCP Server MCP server (sinduja98/sample-mcp-postmessage). 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 →