health.hospital-quality
CMS Care Compare hospital quality ratings (~5,300 Medicare-certified US hospitals): overall star rating + mortality/safety/readmission/patient-experience measure summaries. By facilityId, or state/city/name filters.
This record as markdown: /tools/io-github-2s-io-mcp/health.hospital-quality.md
What health.hospital-quality does on Mcp
AI agents call health.hospital-quality to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health.hospital-quality is rated Low
This tool performs data retrieval and querying of public healthcare quality metrics. It does not create, modify, delete, execute code, or move funds. The queries are search/filter operations that return existing public data without causing any system changes or side effects.
From the tool's definition Tool retrieves hospital quality ratings data from CMS Care Compare (~5,300 hospitals) with filtering options (facilityId, state, city, name).
Attacks that exploit this kind of access
The rule that runs health.hospital-quality safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health.hospital-quality, this is the rule to start with:
health.hospital-quality 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 Mcp, apply this rule, and every health.hospital-quality call is checked against it from then on.
Questions about health.hospital-quality
CMS Care Compare hospital quality ratings (~5,300 Medicare-certified US hospitals): overall star rating + mortality/safety/readmission/patient-experience measure summaries. By facilityId, or state/city/name filters. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for health.hospital-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 Mcp. Nothing to install.
health.hospital-quality 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 health.hospital-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 health.hospital-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.
health.hospital-quality is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue