health.hospital-lookup
CMS Care Compare hospital lookup. Lookup by 6-digit CMS Facility ID, or fuzzy by name + city + state + hospital type with optional min star rating. Returns address, phone, type, ownership, emergency services, overall rating, per-measure-group counts.
This record as markdown: /tools/io-github-2s-io-mcp/health.hospital-lookup.md
What health.hospital-lookup does on Mcp
AI agents call health.hospital-lookup 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-lookup is rated Low
This tool performs read-only lookups against CMS (Centers for Medicare & Medicaid Services) hospital data. It accepts search parameters (facility ID, name, location, type, ratings) and returns informational attributes about hospitals. No side effects, no data modification, no code execution, and no financial operations are possible. The low severity reflects the public nature of CMS data and minimal risk from misuse.
From the tool's definition Tool description states 'Lookup by 6-digit CMS Facility ID' and 'Returns address, phone, type, ownership, emergency services, overall rating, per-measure-group counts' — exclusively retrieves and queries publicly available hospital data with no modification,…
Attacks that exploit this kind of access
The rule that runs health.hospital-lookup 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-lookup, this is the rule to start with:
health.hospital-lookup 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-lookup call is checked against it from then on.
Questions about health.hospital-lookup
CMS Care Compare hospital lookup. Lookup by 6-digit CMS Facility ID, or fuzzy by name + city + state + hospital type with optional min star rating. Returns address, phone, type, ownership, emergency services, overall rating, per-measure-group counts. 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-lookup: 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-lookup 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-lookup 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-lookup. 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-lookup 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