prescriber_ties_profile

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/prescriber-ties-profile.md

WHAT IT DOES

What prescriber_ties_profile does on Livedatalink

AI agents call prescriber_ties_profile to retrieve information from Livedatalink 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`	string	—	Optional exact 10-digit NPI; overrides name search.
`year`	string	—	Optional 4-digit CMS program year (e.g. '2023'); defaults to the most recent year with disclosed payments.
`state`	string	—	Optional 2-letter state to disambiguate the NPPES match (e.g. 'OH').
`last_name`	string	—	Prescriber last name (e.g. 'Nissen'). Provide this or an npi.
`first_name`	string	—	Optional prescriber first name to disambiguate (e.g. 'Steven').

Parameters from the server's own tool schema.

RISK

Why prescriber_ties_profile is rated Low

Even though prescriber_ties_profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prescriber_ties_profile safely

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

prescriber_ties_profile Allowed

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

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

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

FAQ

Questions about prescriber_ties_profile

What does the prescriber_ties_profile tool do? +

One-call identity + industry-financial-ties transparency profile for a US healthcare prescriber. Joins two keyless federal sources: the NPPES NPI Registry (identity - NPI, specialty, city/state, active status) and CMS Open Payments / Sunshine Act (industry payments disclosed to that prescriber - total dollars, payment count, top paying manufacturers, and associated drugs/products for the most recent program year with data). Provide a last_name (ideally with first_name + state) or an exact 10-digit npi. The name resolver picks the NPPES record that genuinely matches the requested name (never a blind top hit), and payments are pinned to that exact NPI across recent program years. This is a TRANSPARENCY profile drawn from public records, NOT a judgment: industry payments to physicians are lawful and publicly disclosed, and their presence is not evidence of wrongdoing. A source that fails is noted, not fatal. Premium cross-source synthesis; verify against the primary sources. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does prescriber_ties_profile accept? +

prescriber_ties_profile accepts 5 parameters: npi, year, state, last_name, first_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prescriber_ties_profile? +

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

What risk level is prescriber_ties_profile? +

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

Can I rate-limit prescriber_ties_profile? +

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

How do I block prescriber_ties_profile completely? +

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

What MCP server provides prescriber_ties_profile? +

prescriber_ties_profile is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

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