AI agents call list_problems to retrieve information from Healow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves problem-list conditions (diagnosis/medical conditions) for a specific patient. While the data returned is sensitive clinical information that could pose privacy/security risks if misused by an AI agent (hence 'medium' severity given the healthcare context and potential for information disclosure), the operation itself is non-destructive and performs no side effects beyond…
From the tool's definition Tool name 'list_problems' and description 'List problem-list Conditions for the launch patient' indicate a retrieval operation that queries existing clinical data. The FHIR Condition resource is being fetched, not created, modified, or deleted.
Attacks that exploit this kind of access
List problem-list Conditions for the launch patient. It is categorised as a Read tool in the Healow MCP Server, which means it retrieves data without modifying state.
Register the Healow MCP server in PolicyLayer and add a rule for list_problems: 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 Healow. Nothing to install.
list_problems 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 list_problems 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 list_problems. 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.
list_problems is provided by the Healow MCP server (voysi-ia/healow-mcp-server). 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 →