cdc_excess_deaths_covid
CDC excess deaths associated with COVID-19 (xkkf-xrst). Modeled expected vs observed deaths by state and week. Used to estimate true pandemic impact beyond reported COVID deaths.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cdc-excess-deaths-covid.md
What cdc_excess_deaths_covid does on Livedatalink
AI agents call cdc_excess_deaths_covid 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 rows (default 50) |
state | string | — | Full state name (e.g. 'Texas') or 'United States' |
outcome | string | — | Outcome (e.g. 'All causes', 'All causes, excluding COVID-19') |
Parameters from the server's own tool schema.
Why cdc_excess_deaths_covid is rated Low
This tool provides read-only access to public health statistics from the CDC. It fetches historical mortality data to compare expected versus observed death counts across states and time periods. There are no side effects, no data modification, no code execution, and no financial implications. The tool supports passive data retrieval and analysis use cases typical of health surveillance dashboards.
From the tool's definition Tool retrieves and queries CDC epidemiological data on excess deaths ("modeled expected vs observed deaths by state and week"). The description indicates data retrieval and analysis functions only, with no capacity to modify, delete, or execute operations.
Attacks that exploit this kind of access
The rule that runs cdc_excess_deaths_covid 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_excess_deaths_covid, this is the rule to start with:
cdc_excess_deaths_covid 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_excess_deaths_covid call is checked against it from then on.
Questions about cdc_excess_deaths_covid
CDC excess deaths associated with COVID-19 (xkkf-xrst). Modeled expected vs observed deaths by state and week. Used to estimate true pandemic impact beyond reported COVID deaths. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cdc_excess_deaths_covid accepts 3 parameters: limit, state, outcome. 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_excess_deaths_covid: 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_excess_deaths_covid 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_excess_deaths_covid 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_excess_deaths_covid. 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_excess_deaths_covid 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