Retrieves a medication request by its unique ID.
AI agents call getMedicationRequestById 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.
This tool performs data retrieval only—it queries and returns a medication request record by identifier. There is no creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is limited to unauthorized viewing of healthcare data, which while sensitive, is less severe than write or destructive operations.
From the tool's definition Tool name 'getMedicationRequestById' and description 'Retrieves a medication request by its unique ID' indicate a read-only operation that fetches existing data without modification or side effects.
Documented attack patterns abuse exactly the kind of access getMedicationRequestById 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 getMedicationRequestById:
{
"version": "1",
"default": "deny",
"tools": {
"getMedicationRequestById": {}
}
} getMedicationRequestById is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves a medication request by its unique ID. It is categorised as a Read tool in the Medplum MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Medplum MCP Server MCP server in PolicyLayer and add a rule for getMedicationRequestById: 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.
getMedicationRequestById is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getMedicationRequestById 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 getMedicationRequestById. 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.
getMedicationRequestById 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.