npi_search_provider
Search individual US healthcare providers by name. Requires a last_name (first_name, state, city optional). Returns NPI, specialty, location for each match.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/npi-search-provider.md
What npi_search_provider does on Livedatalink
AI agents call npi_search_provider 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 |
|---|---|---|---|
city | string | — | City to narrow results (optional). |
limit | number | — | Max results (1-50, default 10). |
state | string | — | Two-letter state code to narrow results (optional). |
last_name | string | Yes | Provider last name (required). |
first_name | string | — | Provider first name (optional). |
Parameters from the server's own tool schema.
Why npi_search_provider is rated Low
The NPI (National Provider Identifier) search queries a public US healthcare registry database and returns read-only information (identifier, specialty, location). This is a straightforward data retrieval tool with no capability to modify data, execute operations, or trigger external side effects.
From the tool's definition Tool performs a 'Search' operation that 'Returns NPI, specialty, location for each match' — it retrieves publicly available healthcare provider registry data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs npi_search_provider 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 npi_search_provider, this is the rule to start with:
npi_search_provider 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 npi_search_provider call is checked against it from then on.
Questions about npi_search_provider
Search individual US healthcare providers by name. Requires a last_name (first_name, state, city optional). Returns NPI, specialty, location for each match. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
npi_search_provider accepts 5 parameters: city, limit, state, last_name, first_name. Required: last_name. 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 npi_search_provider: 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.
npi_search_provider 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 npi_search_provider 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 npi_search_provider. 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.
npi_search_provider 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