Provider 360 by NPI — merges NPPES identity (name, specialty, address, licenses) + CMS Open Payments (industry payments) + CMS Medicare billing in one call. Each section reports found/error independently. KYC, healthcare-fraud, provider due diligence.
AI agents call health.provider-profile to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates sensitive healthcare provider data (name, specialty, address, licenses, payment history, billing records) from multiple authoritative sources. While no data is modified or deleted, the sensitivity of healthcare information and potential for misuse in KYC/fraud detection workflows warrants medium severity.
From the tool's definition Merges and retrieves NPPES identity data, CMS Open Payments, and CMS Medicare billing information in one call. No modifications, deletions, or financial transactions are performed—only aggregated queries and reporting of existing healthcare datasets.
Attacks that exploit this kind of access
Provider 360 by NPI — merges NPPES identity (name, specialty, address, licenses) + CMS Open Payments (industry payments) + CMS Medicare billing in one call. Each section reports found/error independently. KYC, healthcare-fraud, provider due diligence. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for health.provider-profile: 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 Mcp. Nothing to install.
health.provider-profile 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 health.provider-profile 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 health.provider-profile. 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.
health.provider-profile is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →