patient_everything

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

Server Amazon ElastiCache Memcached MCP Server awslabs.memcached-mcp-server
Category Read
Risk class Low
Parameters 00 required

What patient_everything does on Amazon ElastiCache Memcached MCP Server

AI agents call patient_everything to retrieve information from Amazon ElastiCache Memcached MCP Server 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

The $patient-everything operation is a standard FHIR read operation that retrieves multiple related resources for a patient. While this is a Read operation (no modification), the severity is medium rather than low because: (1) it exposes sensitive Protected Health Information (PHI) in healthcare context, and (2) an agent with this tool could potentially access comprehensive patient records across multiple resource…

From the tool's definition Tool retrieves 'all resources related to a specific patient' using FHIR $patient-everything operation. This is a query operation that fetches and aggregates healthcare data with no side effects mentioned.

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 Amazon ElastiCache Memcached MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on patient_everything? +

Register the Amazon ElastiCache Memcached MCP Server 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 Amazon ElastiCache Memcached MCP Server. 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 Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-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.