compliance_fetch_npi_provider

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/compliance-fetch-npi-provider.md

WHAT IT DOES

What compliance_fetch_npi_provider does on DataNexus MCP

AI agents call compliance_fetch_npi_provider to retrieve information from DataNexus MCP 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_number`	string	—	10-digit NPI number e.g. 1003000126. No dashes. Required.

Parameters from the server's own tool schema.

RISK

Why compliance_fetch_npi_provider is rated Low

This tool retrieves NPI (National Provider Identifier) registration information, which is classified as Personally Identifiable Information (PII) related to healthcare providers. While it performs a read-only query with no side effects, the sensitivity of healthcare provider data and the ability to enumerate or collect NPI details justifies a 'high' severity rating.

From the tool's definition Fetch NPI registration details for a US healthcare provider by NPI number. Read-only. No side effects. Idempotent.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compliance_fetch_npi_provider safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compliance_fetch_npi_provider, this is the rule to start with:

compliance_fetch_npi_provider Allowed

compliance_fetch_npi_provider 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": {
    "compliance_fetch_npi_provider": {}
  }
}

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

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

FAQ

Questions about compliance_fetch_npi_provider

What does the compliance_fetch_npi_provider tool do? +

Fetch NPI registration details for a US healthcare provider by NPI number. Read-only. No side effects. Idempotent. US only. npi_number: 10-digit NPI number e.g. 1003000126. Required. Do not include dashes or spaces. Returns provider name, credential type, speciality taxonomy, practice address, and active status. Use this when you have the exact 10-digit NPI. Use compliance_search_npi_by_name instead when you only have the provider name. Verified source: NPPES NPI Registry (CMS). 24-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="compliance_fetch_npi_provider", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.

What parameters does compliance_fetch_npi_provider accept? +

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

How do I enforce a policy on compliance_fetch_npi_provider? +

Register the DataNexus MCP server in PolicyLayer and add a rule for compliance_fetch_npi_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 DataNexus MCP. Nothing to install.

What risk level is compliance_fetch_npi_provider? +

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

Can I rate-limit compliance_fetch_npi_provider? +

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

How do I block compliance_fetch_npi_provider completely? +

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

What MCP server provides compliance_fetch_npi_provider? +

compliance_fetch_npi_provider is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DataNexus, and thousands of servers like it.

This server

All 55 DataNexus tools →

Across the catalogue

fetch_url on 0sec → The MCP Attack Database →

Guides

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