license.medical

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/license.medical.md

WHAT IT DOES

What license.medical does on Mcp

AI agents call license.medical to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why license.medical is rated Low

This tool queries a public healthcare provider registry and returns read-only information. It performs no writes, executions, or financial transactions. The severity is low because it accesses publicly available NPI registry data, though it does aggregate PII-adjacent professional information.

From the tool's definition 'lookup' and 'Returns name, credentials, specialty taxonomies with state license numbers, addresses, phone, identifiers' — purely retrieves data from the NPPES NPI Registry with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs license.medical safely

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

license.medical Allowed

license.medical 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": {
    "license.medical": {}
  }
}

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

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

FAQ

Questions about license.medical

What does the license.medical tool do? +

US healthcare provider lookup (NPPES NPI Registry). Lookup by 10-digit NPI (precise) or firstName + lastName + state. Returns name, credentials, specialty taxonomies with state license numbers, addresses, phone, identifiers. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on license.medical? +

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

What risk level is license.medical? +

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

Can I rate-limit license.medical? +

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

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

license.medical 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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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