Reads a FHIR resource from a FHIR server given a resource type and resource
AI agents call read_fhir_resource to retrieve information from Cardiovascular Disease without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves FHIR (Fast Healthcare Interoperability Resources) records, which are structured healthcare data containing sensitive patient health information (PHI). While the action itself is read-only with no side effects, the severity is high because FHIR resources typically contain protected health information such as diagnoses, medications, lab results, and personal identifiers.
From the tool's definition Tool name 'read_fhir_resource' and description 'Reads a FHIR resource from a FHIR server given a resource type and resource' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Reads a FHIR resource from a FHIR server given a resource type and resource. It is categorised as a Read tool in the Cardiovascular Disease MCP Server, which means it retrieves data without modifying state.
Register the Cardiovascular Disease MCP server in PolicyLayer and add a rule for read_fhir_resource: 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 Cardiovascular Disease. Nothing to install.
read_fhir_resource 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 read_fhir_resource 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 read_fhir_resource. 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.
read_fhir_resource is provided by the Cardiovascular Disease MCP server (jamesvdinh/cardiovascular-disease-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →