Add a new allergy to patient records
AI agents use addAllergy 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 creates new allergy entries in patient records, which is a reversible write operation. While not destructive (data can be modified or removed), it modifies critical healthcare data that could affect clinical decision-making and patient safety if incorrect allergies are added (e.g., false allergies could cause unnecessary treatment restrictions; missing real allergies could lead to harmful drug…
From the tool's definition Tool name 'addAllergy' and description 'Add a new allergy to patient records' indicate creation of new data in a medical record system.
Attacks that exploit this kind of access
Add a new allergy to patient records. 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 addAllergy: 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.
addAllergy 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 addAllergy 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 addAllergy. 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.
addAllergy 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 →