cms_home_health_search
Search Medicare-certified home health agencies from CMS Home Health Compare. Returns agency name, address, services offered, and quality ratings.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cms-home-health-search.md
What cms_home_health_search does on Livedatalink
AI agents call cms_home_health_search to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 25) |
state | string | — | Two-letter state code (e.g. 'CA', 'NY') |
offset | number | — | Pagination offset (default 0) |
name_contains | string | — | Partial provider name match |
Parameters from the server's own tool schema.
Why cms_home_health_search is rated Low
This tool queries a public Medicare database (CMS Home Health Compare) and retrieves informational data about certified agencies. There are no side effects, no data modification, no destructive actions, and no financial transactions. It is a straightforward read/search operation with minimal risk even if misused by an AI agent, as the worst outcome would be inappropriate or excessive queries against public data.
From the tool's definition Tool performs a search and returns agency name, address, services offered, and quality ratings—all retrieval operations with no modification, deletion, or external execution. The description uses 'search' and 'returns', indicating a query-only operation.
Attacks that exploit this kind of access
The rule that runs cms_home_health_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cms_home_health_search, this is the rule to start with:
cms_home_health_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every cms_home_health_search call is checked against it from then on.
Questions about cms_home_health_search
Search Medicare-certified home health agencies from CMS Home Health Compare. Returns agency name, address, services offered, and quality ratings. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cms_home_health_search accepts 4 parameters: limit, state, offset, name_contains. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for cms_home_health_search: 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 Livedatalink. Nothing to install.
cms_home_health_search 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 cms_home_health_search 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 cms_home_health_search. 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.
cms_home_health_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue