npi_lookup
Look up a single US healthcare provider by their 10-digit NPI (National Provider Identifier). Returns name, type, credential, primary specialty (taxonomy), practice location, and status. Keyless CMS data.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/npi-lookup.md
What npi_lookup does on Livedatalink
AI agents call npi_lookup 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 |
|---|---|---|---|
npi | string | Yes | 10-digit NPI number. |
Parameters from the server's own tool schema.
Why npi_lookup is rated Low
This tool performs a simple data lookup query against public US healthcare provider records (National Provider Identifier database maintained by CMS). It retrieves information only and has no capability to modify, delete, or execute operations. The data returned (name, credentials, location, status) is public information already available through official CMS channels.
From the tool's definition Tool description states 'Look up a single US healthcare provider' and 'Returns name, type, credential, primary specialty, practice location, and status.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs npi_lookup 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_lookup, this is the rule to start with:
npi_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 Livedatalink, apply this rule, and every npi_lookup call is checked against it from then on.
Questions about npi_lookup
Look up a single US healthcare provider by their 10-digit NPI (National Provider Identifier). Returns name, type, credential, primary specialty (taxonomy), practice location, and status. Keyless CMS data. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
npi_lookup accepts 1 parameter: npi. Required: npi. 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_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 Livedatalink. Nothing to install.
npi_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 npi_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 npi_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.
npi_lookup 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