facility_care_quality
One-call care-quality + provider-identity read for a named US healthcare FACILITY (hospital, nursing home, home-health agency, or hospice). Joins two keyless federal sources: CMS Care Compare (data.cms.gov) for the facility's quality signal - the CMS star rating and, for a hospital, the measure-g...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/facility-care-quality.md
What facility_care_quality does on Livedatalink
AI agents use facility_care_quality to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Optional provider category to pin the CMS dataset: 'hospital', 'nursing_home', 'home_health', or 'hospice'. Omit to auto-detect. |
state | string | — | Optional 2-letter state to disambiguate the facility (e.g. 'OH', 'AZ'). |
facility | string | Yes | Facility name to look up (e.g. 'Cleveland Clinic', 'Mayo Clinic Hospital', 'Burns Nursing Home'). |
Parameters from the server's own tool schema.
Why facility_care_quality is rated Medium
An AI agent can call facility_care_quality faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs facility_care_quality 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 facility_care_quality, this is the rule to start with:
facility_care_quality stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 facility_care_quality call is checked against it from then on.
Questions about facility_care_quality
One-call care-quality + provider-identity read for a named US healthcare FACILITY (hospital, nursing home, home-health agency, or hospice). Joins two keyless federal sources: CMS Care Compare (data.cms.gov) for the facility's quality signal - the CMS star rating and, for a hospital, the measure-group highlights (mortality, safety of care, readmission, timely-and-effective care measured better / no different / worse vs national), plus ownership, type, and for a nursing home the health-inspection / staffing / quality-measure star breakdown, certified beds, abuse flag, and fines - and the NPPES NPI Registry for the facility's legal identity (organizational NPI, taxonomy, city/state, active status). Provide a facility name (e.g. 'Cleveland Clinic', 'Mayo Clinic Hospital'); optionally add a 2-letter state to disambiguate and a type (hospital / nursing_home / home_health / hospice) to pin the CMS dataset. When no type is given the tool infers the provider category from the NPPES taxonomy and probes the CMS datasets in order. A leg that fails is noted, not fatal. This is an INFORMATIONAL public-record read, NOT medical advice, a substitute for CMS Care Compare, or an endorsement of any facility. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
facility_care_quality accepts 3 parameters: type, state, facility. Required: facility. 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 facility_care_quality: 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.
facility_care_quality is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the facility_care_quality 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 facility_care_quality. 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.
facility_care_quality 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