List all available health data adapters and their authentication status.
AI agents call list_adapters to retrieve information from Health 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 and displays information about available adapters and their authentication status. It has no side effects, does not execute code or commands, does not modify data, and does not access financial information. It is a simple informational query, making it a Read category tool with low severity since the information disclosed (adapter names and auth status) has minimal blast radius for misuse.
From the tool's definition Tool name 'list_adapters' and description 'List all available health data adapters and their authentication status' indicate a pure query/retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List all available health data adapters and their authentication status. It is categorised as a Read tool in the Health MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Health MCP Server MCP server in PolicyLayer and add a rule for list_adapters: 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 Health MCP Server. Nothing to install.
list_adapters 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_adapters 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_adapters. 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_adapters is provided by the Health MCP Server MCP server (marholoubek/health_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 →