Assess the data quality and integrity of the FHIR server
AI agents call assess_data_quality 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.
Data quality assessment tools retrieve and analyze information about data integrity but do not create, modify, delete, or execute external operations. However, the severity is elevated to 'medium' rather than 'low' because the tool operates on a healthcare FHIR system containing sensitive patient data; misuse could reveal information about data quality issues, missing records, or system vulnerabilities that could be…
From the tool's definition The tool name 'assess_data_quality' and description 'Assess the data quality and integrity of the FHIR server' indicate a diagnostic/inspection operation that queries and analyzes existing data without modification.
Attacks that exploit this kind of access
Assess the data quality and integrity of the FHIR server. 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 assess_data_quality: 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.
assess_data_quality 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 assess_data_quality 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 assess_data_quality. 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.
assess_data_quality is provided by the FHIR MCP Server MCP server (jcafazzo/fhir-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 →