cdc_outbreak_reports
CDC NORS foodborne / waterborne / enteric outbreak reports (iezt-77pi). Returns outbreak date, state, etiology, illnesses, hospitalizations, deaths, and implicated food/exposure.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cdc-outbreak-reports.md
What cdc_outbreak_reports does on Livedatalink
AI agents call cdc_outbreak_reports 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 | — | Outbreak year |
limit | number | — | Max rows (default 50) |
state | string | — | Full state name |
etiology | string | — | Causative agent (e.g. 'Salmonella', 'Norovirus', 'E. coli') |
Parameters from the server's own tool schema.
Why cdc_outbreak_reports is rated Low
This tool queries and retrieves read-only epidemiological data from the CDC NORS (National Outbreak Reporting System) database. It performs no data modification, deletion, execution of arbitrary code, financial transactions, or irreversible actions. The data returned is public health information intended for research and awareness.
From the tool's definition Tool description indicates it 'Returns outbreak date, state, etiology, illnesses, hospitalizations, deaths, and implicated food/exposure' — purely retrieves historical public health data from CDC NORS without modification or deletion capabilities.
Attacks that exploit this kind of access
The rule that runs cdc_outbreak_reports 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_outbreak_reports, this is the rule to start with:
cdc_outbreak_reports 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_outbreak_reports call is checked against it from then on.
Questions about cdc_outbreak_reports
CDC NORS foodborne / waterborne / enteric outbreak reports (iezt-77pi). Returns outbreak date, state, etiology, illnesses, hospitalizations, deaths, and implicated food/exposure. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cdc_outbreak_reports accepts 4 parameters: year, limit, state, etiology. 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_outbreak_reports: 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_outbreak_reports 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_outbreak_reports 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_outbreak_reports. 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_outbreak_reports 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