AI agents use updatePatient to create or update resources in Medplum MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Medplum MCP Server environment.
This tool creates or modifies patient data reversibly, which is the defining characteristic of the Write category. Although the data modified is sensitive healthcare information (which elevates severity to high due to potential HIPAA violations, privacy breaches, or incorrect medical records if misused), the operation itself is not irreversible (Destructive), does not execute arbitrary code (Execute), and does not…
From the tool's definition Tool name is 'updatePatient' and description states 'Updates an existing patient' — this modifies existing data in a healthcare system.
Documented attack patterns abuse exactly the kind of access updatePatient gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Medplum MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for updatePatient:
{
"version": "1",
"default": "deny",
"tools": {
"updatePatient": {
"limits": [
{
"counter": "updatepatient_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} updatePatient stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Updates an existing patient. It is categorised as a Write tool in the Medplum MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Medplum MCP Server MCP server in PolicyLayer and add a rule for updatePatient: 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 Medplum MCP Server. Nothing to install.
updatePatient 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 updatePatient 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 updatePatient. 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.
updatePatient is provided by the Medplum MCP Server MCP server (rkirkendall/medplum-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Medplum MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Medplum MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.