cms_nursing_home_search
Search Medicare-certified nursing homes from CMS Nursing Home Compare. Returns name, address, ownership, certification status, total beds, and quality measures.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cms-nursing-home-search.md
What cms_nursing_home_search does on Livedatalink
AI agents call cms_nursing_home_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_nursing_home_search is rated Low
This tool queries and retrieves publicly available nursing home data from CMS (Centers for Medicare & Medicaid Services) without modifying, creating, deleting, or executing any operations. It is a pure data lookup/search function with no side effects or state changes. The blast radius of misuse is minimal—an AI agent could retrieve information but cannot harm healthcare records or systems.
From the tool's definition Tool description states 'Search Medicare-certified nursing homes' and 'Returns name, address, ownership, certification status, total beds, and quality measures' — these are read-only retrieval operations with no modification or deletion capabilities.
Attacks that exploit this kind of access
The rule that runs cms_nursing_home_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_nursing_home_search, this is the rule to start with:
cms_nursing_home_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_nursing_home_search call is checked against it from then on.
Questions about cms_nursing_home_search
Search Medicare-certified nursing homes from CMS Nursing Home Compare. Returns name, address, ownership, certification status, total beds, and quality measures. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cms_nursing_home_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_nursing_home_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_nursing_home_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_nursing_home_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_nursing_home_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_nursing_home_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