createPractitioner

THE RISK

Medium Risk

Why createPractitioner needs a policy

This tool creates new healthcare provider records in a FHIR-compliant medical database. While the immediate action is reversible (the record can be updated or logically deleted), creating practitioner records in a healthcare system carries high severity due to the sensitivity of healthcare data and the potential for unauthorized practitioner registration, which could enable fraudulent medical activities, privacy…

From the tool's definition Tool name is 'createPractitioner' and description states it 'Creates a new medical practitioner.' The verb 'Creates' and the tool name prefix 'create' unambiguously indicate a write operation that adds new data to the FHIR server.

Documented attack patterns abuse exactly the kind of access createPractitioner gives an agent:

POLICY

How to control createPractitioner

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 createPractitioner:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "createPractitioner": {
      "limits": [
        {
          "counter": "createpractitioner_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

createPractitioner 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.

Create a free account and register Medplum MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Medplum MCP Server tools

Write createCondition Creates a new condition or diagnosis for a patient. Requires a patient ID and a condition Write createEncounter Creates a new encounter (patient visit). Requires patient ID and status. Write createEpisodeOfCare Creates a new episode of care for a patient. Requires patient ID and status. Write createMedication Creates a new medication resource. Requires medication code or identifier. Write createMedicationRequest Creates a new medication request (prescription). Requires patient ID, medication reference Write createObservation Creates a new observation (lab result, vital sign, etc.). Requires patient ID and code. Write createOrganization Creates a new organization (e.g., hospital, clinic). Requires organization name. Write createPatient Creates a new patient resource. Requires first name, last name, and birth date.

All 37 Medplum MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about createPractitioner

What does the createPractitioner tool do? +

Creates a new medical practitioner. Requires given name and family name. 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.

How do I enforce a policy on createPractitioner? +

Register the Medplum MCP Server MCP server in PolicyLayer and add a rule for createPractitioner: 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.

What risk level is createPractitioner? +

createPractitioner is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit createPractitioner? +

Yes. Add a rate_limit block to the createPractitioner 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.

How do I block createPractitioner completely? +

Set action: deny in the PolicyLayer policy for createPractitioner. 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.

What MCP server provides createPractitioner? +

createPractitioner 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.

Enforce policy on every Medplum MCP Server tool call.

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.

CHECK YOUR STACK →