compliance_search_npi_by_name

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 30 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-search-npi-by-name.md

WHAT IT DOES

What compliance_search_npi_by_name does on DataNexus MCP

AI agents call compliance_search_npi_by_name 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
`name`	string	—	Full or partial provider name. Required.
`state`	string	—	Two-letter US state code e.g. CA. Optional.
`speciality`	string	—	Speciality keyword e.g. Cardiology. Optional.

Parameters from the server's own tool schema.

RISK

Why compliance_search_npi_by_name is rated Low

This tool retrieves healthcare provider data (NPI - National Provider Identifier information) from a public registry without modifying, executing code, or causing irreversible changes. It is clearly a Read operation.

From the tool's definition Tool description explicitly states: 'Search the NPPES NPI Registry by provider name' and 'Read-only. No side effects. Idempotent.' Returns NPI number, name, specialty, and address for matches.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

compliance_search_npi_by_name Allowed

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

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_search_npi_by_name call is checked against it from then on.

FAQ

Questions about compliance_search_npi_by_name

What does the compliance_search_npi_by_name tool do? +

Search the NPPES NPI Registry by provider name with optional state and speciality filters. Read-only. No side effects. Idempotent. US only. Returns up to 10 matches. name: Full or partial provider name. Required. state: Two-letter US state code e.g. CA. Optional. speciality: Speciality keyword e.g. Cardiology. Optional. Returns NPI number, name, speciality, and address for each match. Use this when you do not have the NPI number. Use compliance_fetch_npi_provider instead when you have the exact 10-digit NPI. 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_search_npi_by_name", 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_search_npi_by_name accept? +

compliance_search_npi_by_name accepts 3 parameters: name, state, speciality. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on compliance_search_npi_by_name? +

Register the DataNexus MCP server in PolicyLayer and add a rule for compliance_search_npi_by_name: 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_search_npi_by_name? +

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

Can I rate-limit compliance_search_npi_by_name? +

Yes. Add a rate_limit block to the compliance_search_npi_by_name 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_search_npi_by_name completely? +

Set action: deny in the PolicyLayer policy for compliance_search_npi_by_name. 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_search_npi_by_name? +

compliance_search_npi_by_name 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

get_cocktail_by_name on Cocktails RAG MCP Server →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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