Low Risk

getPatientById

Retrieves a patient resource by their unique ID.

How to control getPatientById ↓

What getPatientById does on Medplum MCP Server

AI agents call getPatientById to retrieve information from Medplum MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getPatientById needs a policy

This tool performs a read-only operation that retrieves healthcare data (patient information) from a FHIR server. While the severity is elevated to 'medium' rather than 'low' due to the sensitivity of personal health information (PHI) being accessed, it does not create, modify, delete, or execute any operations—it only retrieves existing data.

From the tool's definition Tool name 'getPatientById' and description 'Retrieves a patient resource by their unique ID' indicate a retrieval operation with no modification of data.

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

How to control getPatientById

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getPatientById": {}
  }
}

getPatientById is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getPatientById

What does the getPatientById tool do? +

Retrieves a patient resource by their unique ID. It is categorised as a Read tool in the Medplum MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getPatientById? +

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

getPatientById is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getPatientById? +

Yes. Add a rate_limit block to the getPatientById 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 getPatientById completely? +

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

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

Free to start. No card required.

37 Medplum MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.