patient_everything

Retrieve all resources related to a specific patient using the FHIR $patient-everything operation

Server Awslabs Valkey awslabs.valkey-mcp-server
Category Read
Risk class Low
Parameters 00 required

What patient_everything does on Awslabs Valkey

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

Why patient_everything needs a policy

This tool retrieves patient data without modifying, deleting, or executing arbitrary operations. However, severity is high because it accesses sensitive protected health information (PHI) for an entire patient record across all FHIR resource types. Misuse by an AI agent could result in unauthorized disclosure of comprehensive patient medical history, diagnoses, medications, and treatments.

From the tool's definition Tool description states 'Retrieve all resources related to a specific patient' using a standard FHIR read operation ($patient-everything). The verb 'Retrieve' and lack of any modification language confirms read-only intent.

Questions about patient_everything

What does the patient_everything tool do? +

Retrieve all resources related to a specific patient using the FHIR $patient-everything operation. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on patient_everything? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for patient_everything: 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 Awslabs Valkey. Nothing to install.

What risk level is patient_everything? +

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

Can I rate-limit patient_everything? +

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

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

patient_everything is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.