npi_search_specialty
Find healthcare providers by specialty (taxonomy description) in a location. Requires taxonomy (e.g. 'Cardiology', 'Pediatrics', 'Nurse Practitioner'); state and city optional but recommended.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/npi-search-specialty.md
What npi_search_specialty does on Livedatalink
AI agents call npi_search_specialty 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). |
taxonomy | string | Yes | Specialty / taxonomy description, e.g. 'Cardiology'. |
Parameters from the server's own tool schema.
Why npi_search_specialty is rated Low
This tool retrieves healthcare provider information based on search criteria. It has no side effects—it does not create, modify, delete, or execute any operations. The severity is low because the data returned would be publicly available provider information, and there is minimal risk of harm from an AI agent querying this data.
From the tool's definition Tool performs a search query to 'Find healthcare providers by specialty' with parameters like taxonomy, state, and city. The description indicates it retrieves or queries data without modifying anything.
Attacks that exploit this kind of access
The rule that runs npi_search_specialty 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_specialty, this is the rule to start with:
npi_search_specialty 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_specialty call is checked against it from then on.
Questions about npi_search_specialty
Find healthcare providers by specialty (taxonomy description) in a location. Requires taxonomy (e.g. 'Cardiology', 'Pediatrics', 'Nurse Practitioner'); state and city optional but recommended. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
npi_search_specialty accepts 4 parameters: city, limit, state, taxonomy. Required: taxonomy. 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_specialty: 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_specialty 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_specialty 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_specialty. 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_specialty 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