cdc_leading_causes_of_death
NCHS leading causes of death by state (bi63-dtpu). Returns total deaths and age-adjusted death rates per cause per state per year. Useful for chronic disease + injury mortality research.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cdc-leading-causes-of-death.md
What cdc_leading_causes_of_death does on Livedatalink
AI agents call cdc_leading_causes_of_death 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 |
|---|---|---|---|
year | number | — | Year |
limit | number | — | Max rows (default 50) |
state | string | — | Full state name or 'United States' |
cause_name | string | — | Cause name (e.g. 'Heart disease', 'Cancer', 'Suicide') |
Parameters from the server's own tool schema.
Why cdc_leading_causes_of_death is rated Low
This tool retrieves public health statistics without side effects. While the topic is health-sensitive, the tool only performs read operations—retrieving, not modifying or executing—and returns historical statistical data intended for research. No irreversible changes, code execution, financial transactions, or destructive operations are involved.
From the tool's definition Returns total deaths and age-adjusted death rates per cause per state per year. Uses descriptive verbs like 'returns' and has no mention of modifications, deletion, or external actions being triggered.
Attacks that exploit this kind of access
The rule that runs cdc_leading_causes_of_death 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 cdc_leading_causes_of_death, this is the rule to start with:
cdc_leading_causes_of_death 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 cdc_leading_causes_of_death call is checked against it from then on.
Questions about cdc_leading_causes_of_death
NCHS leading causes of death by state (bi63-dtpu). Returns total deaths and age-adjusted death rates per cause per state per year. Useful for chronic disease + injury mortality research. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cdc_leading_causes_of_death accepts 4 parameters: year, limit, state, cause_name. 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 cdc_leading_causes_of_death: 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.
cdc_leading_causes_of_death 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 cdc_leading_causes_of_death 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 cdc_leading_causes_of_death. 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.
cdc_leading_causes_of_death 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