cdc_drug_overdose_deaths
CDC drug overdose deaths by state and indicator (9j2v-jamp). 12-month rolling counts. Useful for opioid/fentanyl/stimulant policy research and treatment-program siting.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cdc-drug-overdose-deaths.md
What cdc_drug_overdose_deaths does on Livedatalink
AI agents call cdc_drug_overdose_deaths 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) |
indicator | string | — | Drug class (e.g. 'Opioids (T40.0-T40.4,T40.6)', 'Synthetic opioids, excl. methadone (T40.4)') |
state_name | string | — | Full state name |
Parameters from the server's own tool schema.
Why cdc_drug_overdose_deaths is rated Low
This tool queries and retrieves public health data from the CDC. It performs no write, execute, destructive, or financial operations. The data it surfaces is epidemiological statistics used for analysis and research, not for operational changes.
From the tool's definition The tool retrieves CDC drug overdose death statistics by state and indicator (9j2v-jamp). The description uses query-oriented language: 'by state and indicator,' '12-month rolling counts,' indicating data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs cdc_drug_overdose_deaths 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_drug_overdose_deaths, this is the rule to start with:
cdc_drug_overdose_deaths 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_drug_overdose_deaths call is checked against it from then on.
Questions about cdc_drug_overdose_deaths
CDC drug overdose deaths by state and indicator (9j2v-jamp). 12-month rolling counts. Useful for opioid/fentanyl/stimulant policy research and treatment-program siting. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cdc_drug_overdose_deaths accepts 3 parameters: limit, indicator, state_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_drug_overdose_deaths: 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_drug_overdose_deaths 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_drug_overdose_deaths 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_drug_overdose_deaths. 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_drug_overdose_deaths 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