getHospitals
Returns US hospitals matching a name, city, state, ZIP code, county or latitude/longitude bounding box, with location, contact information and bed count.
This record as markdown: /tools/com-api-ninjas-mcp/gethospitals.md
What getHospitals does on API Ninjas
AI agents call getHospitals to retrieve information from API Ninjas 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 |
|---|---|---|---|
city | string | — | City where the hospital is located. |
name | string | — | Name of the hospital to search for. Supports partial matching. |
limit | integer | — | Number of results to return. Default is 5. Maximum is 100. |
state | string | — | State where the hospital is located. |
county | string | — | County where the hospital is located. |
offset | integer | — | Number of results to skip. Default is 0. |
zipcode | string | — | ZIP code of the hospital location. |
max_latitude | number | — | Maximum latitude coordinate. |
min_latitude | number | — | Minimum latitude coordinate. |
max_longitude | number | — | Maximum longitude coordinate. |
min_longitude | number | — | Minimum longitude coordinate. |
Parameters from the server's own tool schema.
Why getHospitals is rated Low
Even though getHospitals only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs getHospitals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getHospitals, this is the rule to start with:
getHospitals 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 API Ninjas, apply this rule, and every getHospitals call is checked against it from then on.
Questions about getHospitals
Returns US hospitals matching a name, city, state, ZIP code, county or latitude/longitude bounding box, with location, contact information and bed count. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getHospitals accepts 11 parameters: city, name, limit, state, county, offset, zipcode, max_latitude, min_latitude, max_longitude, min_longitude. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getHospitals: 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 API Ninjas. Nothing to install.
getHospitals 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 getHospitals 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 getHospitals. 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.
getHospitals is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue