Test connectivity to a FHIR server
AI agents call test_server_connectivity to retrieve information from FHIR Careplan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool tests server connectivity, which is a read-only diagnostic operation that queries whether a FHIR server is reachable. It has no side effects on data, does not execute code or commands, does not modify records, and does not create financial obligations. The minimal blast radius (connection timeout or status response) and lack of data handling or state changes justify a 'Read' classification with low severity.
From the tool's definition Tool name and description indicate a diagnostic operation: 'test_server_connectivity' with description 'Test connectivity to a FHIR server'.
Attacks that exploit this kind of access
Test connectivity to a FHIR server. It is categorised as a Read tool in the FHIR Careplan MCP Server, which means it retrieves data without modifying state.
Register the FHIR Careplan MCP server in PolicyLayer and add a rule for test_server_connectivity: 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 Careplan. Nothing to install.
test_server_connectivity 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 test_server_connectivity 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 test_server_connectivity. 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.
test_server_connectivity is provided by the FHIR Careplan MCP server (kushagra-dutta/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 →