open_payments_national_summary
National-level Open Payments totals and averages across all years. Shows how much money flows from pharma to doctors nationally, broken down by payment-nature category.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/open-payments-national-summary.md
What open_payments_national_summary does on Livedatalink
AI agents call open_payments_national_summary 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.
Why open_payments_national_summary is rated Low
This tool fetches aggregated, read-only public data from the Open Payments dataset. It performs no writes, executions, or financial transactions; it only reports statistics about financial flows that already occurred. Misuse potential is minimal.
From the tool's definition 'National-level Open Payments totals and averages across all years. Shows how much money flows from pharma to doctors nationally' — purely retrieves and summarizes existing public data
Attacks that exploit this kind of access
The rule that runs open_payments_national_summary 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_national_summary, this is the rule to start with:
open_payments_national_summary 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_national_summary call is checked against it from then on.
Questions about open_payments_national_summary
National-level Open Payments totals and averages across all years. Shows how much money flows from pharma to doctors nationally, broken down by payment-nature category. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
Register the Livedatalink MCP server in PolicyLayer and add a rule for open_payments_national_summary: 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_national_summary 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_national_summary 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_national_summary. 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_national_summary 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