Low Risk

searchObservations

Searches for observations based on criteria like patient ID or code.

How to control searchObservations ↓

What searchObservations does on Medplum MCP Server

AI agents call searchObservations 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 searchObservations needs a policy

This tool retrieves healthcare observation data based on query parameters (patient ID, code) without creating, modifying, or deleting records. It is a query operation with no side effects, fitting the 'Read' category.

From the tool's definition Tool name is 'searchObservations' and description states it 'Searches for observations based on criteria like patient ID or code.' The verb 'searches' and the read-only nature of retrieving observations with no modification capability.

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

How to control searchObservations

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

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

searchObservations 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 searchObservations

What does the searchObservations tool do? +

Searches for observations based on criteria like patient ID or code. 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 searchObservations? +

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

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

Can I rate-limit searchObservations? +

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

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

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