leie_lookup_npi

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/leie-lookup-npi.md

WHAT IT DOES

What leie_lookup_npi does on Livedatalink

AI agents call leie_lookup_npi 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	Exactly 10 digits; placeholder NPI 0000000000 is rejected.

Parameters from the server's own tool schema.

RISK

Why leie_lookup_npi is rated Low

Even though leie_lookup_npi 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs leie_lookup_npi 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 leie_lookup_npi, this is the rule to start with:

leie_lookup_npi Allowed

leie_lookup_npi is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "leie_lookup_npi": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every leie_lookup_npi call is checked against it from then on.

FAQ

Questions about leie_lookup_npi

What does the leie_lookup_npi tool do? +

Check a 10-digit NPI against the self-hosted HHS OIG List of Excluded Individuals/Entities (LEIE). Returns matching exclusion records with source freshness and evidence IDs. A match is a screening lead, not final identity confirmation; verify it with HHS OIG. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does leie_lookup_npi accept? +

leie_lookup_npi accepts 1 parameter: npi. Required: npi. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on leie_lookup_npi? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for leie_lookup_npi: 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.

What risk level is leie_lookup_npi? +

leie_lookup_npi is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit leie_lookup_npi? +

Yes. Add a rate_limit block to the leie_lookup_npi 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.

How do I block leie_lookup_npi completely? +

Set action: deny in the PolicyLayer policy for leie_lookup_npi. 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.

What MCP server provides leie_lookup_npi? +

leie_lookup_npi 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →