Retrieve a specific diagnostic report by ID.
AI agents call get_diagnostic_report_by_id to retrieve information from FHIR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic reports from a FHIR API without side effects. While the severity is elevated to 'high' due to the sensitive nature of healthcare data (diagnostic reports may contain protected health information including test results, imaging findings, and clinical interpretations that could enable privacy violations or discrimination if accessed inappropriately), the tool itself performs a read-only…
From the tool's definition Tool name 'get_diagnostic_report_by_id' and description 'Retrieve a specific diagnostic report by ID' indicate a query operation that retrieves healthcare data without modification.
Attacks that exploit this kind of access
Retrieve a specific diagnostic report by ID. It is categorised as a Read tool in the FHIR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FHIR MCP Server MCP server in PolicyLayer and add a rule for get_diagnostic_report_by_id: 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 FHIR MCP Server. Nothing to install.
get_diagnostic_report_by_id 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 get_diagnostic_report_by_id 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 get_diagnostic_report_by_id. 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.
get_diagnostic_report_by_id is provided by the FHIR MCP Server MCP server (sdesani/mcp-fhir). 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 →