Low Risk

get_leading_causes_of_death

Get leading causes of death with death counts and age-adjusted rates. Returns data from the NCHS Leading Causes of Death dataset, which provides national and state-level mortality statistics by cause of death, year, and age-adjusted death rate per 100,000 population. Data spans 1999-2017. Args: s...

Part of the CDC Mortality (WONDER) server.

get_leading_causes_of_death is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CDC MORTALITY (WONDER) →

Free to start. No card required.

AI agents call get_leading_causes_of_death to retrieve information from CDC Mortality (WONDER) without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_leading_causes_of_death only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_leading_causes_of_death": {}
  }
}

See the full CDC Mortality (WONDER) policy for all 5 tools.

Get this rule live on your own CDC Mortality (WONDER) server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CDC MORTALITY (WONDER) →

These attack patterns abuse exactly the kind of access get_leading_causes_of_death gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_leading_causes_of_death only ever does what you allow.

SECURE CDC MORTALITY (WONDER) →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_leading_causes_of_death tool do? +

Get leading causes of death with death counts and age-adjusted rates. Returns data from the NCHS Leading Causes of Death dataset, which provides national and state-level mortality statistics by cause of death, year, and age-adjusted death rate per 100,000 population. Data spans 1999-2017. Args: state: Filter by state name (e.g. 'California', 'Texas'). Case-insensitive. Returns all states if not specified. year: Filter by year (e.g. 2017). Returns all available years if not specified. limit: Maximum number of records to return (default 25, max 1000).. It is categorised as a Read tool in the CDC Mortality (WONDER) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_leading_causes_of_death? +

Register the CDC Mortality (WONDER) MCP server in PolicyLayer and add a rule for get_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 CDC Mortality (WONDER). Nothing to install.

What risk level is get_leading_causes_of_death? +

get_leading_causes_of_death is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_leading_causes_of_death? +

Yes. Add a rate_limit block to the get_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.

How do I block get_leading_causes_of_death completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_leading_causes_of_death? +

get_leading_causes_of_death is provided by the CDC Mortality (WONDER) MCP server (https://mcp.olyport.com/cdc-wonder/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CDC Mortality (WONDER) tool call.

Deterministic rules across all 5 CDC Mortality (WONDER) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.