AI agents call medical.provider-id-resolve 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.
The tool performs a read-only lookup of National Provider Identifier (NPI) data from NPPES and NUCC registries, returning provider identity and specialty information. This is a straightforward data retrieval operation with no write, execute, or financial implications.
From the tool's definition 'Resolve an NPI to provider identity + every taxonomy decoded to specialty (NPPES + NUCC)' — pure lookup/resolution of provider identity data from public registries, no side effects
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Resolve an NPI to provider identity + every taxonomy decoded to specialty (NPPES + NUCC). CCN deferred. 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 medical.provider-id-resolve: 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.
medical.provider-id-resolve 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 medical.provider-id-resolve 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 medical.provider-id-resolve. 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.
medical.provider-id-resolve 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 →