open_payments_by_specialty
Payment totals grouped by medical specialty. Reveals which specialties receive the most pharma money: orthopedic surgeons, cardiologists, psychiatrists, etc.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/open-payments-by-specialty.md
What open_payments_by_specialty does on Livedatalink
AI agents call open_payments_by_specialty 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 |
|---|---|---|---|
limit | number | — | Max specialties (default 50) |
Parameters from the server's own tool schema.
Why open_payments_by_specialty is rated Low
This tool retrieves and aggregates publicly available Open Payments data by medical specialty. It is a read-only query returning statistical summaries; no data is created, modified, or deleted. Severity is low as misuse has minimal blast radius — it only exposes aggregated public records.
From the tool's definition Payment totals grouped by medical specialty. Reveals which specialties receive the most pharma money
Attacks that exploit this kind of access
The rule that runs open_payments_by_specialty 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 open_payments_by_specialty, this is the rule to start with:
open_payments_by_specialty is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every open_payments_by_specialty call is checked against it from then on.
Questions about open_payments_by_specialty
Payment totals grouped by medical specialty. Reveals which specialties receive the most pharma money: orthopedic surgeons, cardiologists, psychiatrists, etc. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
open_payments_by_specialty accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for open_payments_by_specialty: 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.
open_payments_by_specialty 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 open_payments_by_specialty 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 open_payments_by_specialty. 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.
open_payments_by_specialty 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.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue