adw.county_mortality
Composite county mortality risk index (ADW-305) including premature death, suicide, overdose, and inverted life expectancy from County Health Rankings + NCI. Returns national percentile rank and band. Pass county as a 5-digit county FIPS (e.g. '12011') or 'County Name, ST' (e.g. 'Lee County, FL')...
This record as markdown: /tools/com-alpinedataworks-adw-intelligence-server/adw.county-mortality.md
What adw.county_mortality does on AlpineDataWorks Intelligence Server
AI agents call adw.county_mortality to retrieve information from AlpineDataWorks Intelligence Server 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 |
|---|---|---|---|
county | string | Yes | 5-digit county FIPS (e.g. '12011') or 'County Name, ST' (e.g. 'Lee County, FL'). |
Parameters from the server's own tool schema.
Why adw.county_mortality is rated Low
This tool queries and retrieves pre-computed health statistics (mortality indices, life expectancy) from existing indices (County Health Rankings + NCI). It performs no write, execute, destructive, or financial operations.
From the tool's definition Tool description indicates it 'Returns national percentile rank and band' for mortality data — a retrieval operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
The rule that runs adw.county_mortality safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AlpineDataWorks Intelligence Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adw.county_mortality, this is the rule to start with:
adw.county_mortality 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 AlpineDataWorks Intelligence Server, apply this rule, and every adw.county_mortality call is checked against it from then on.
Questions about adw.county_mortality
Composite county mortality risk index (ADW-305) including premature death, suicide, overdose, and inverted life expectancy from County Health Rankings + NCI. Returns national percentile rank and band. Pass county as a 5-digit county FIPS (e.g. '12011') or 'County Name, ST' (e.g. 'Lee County, FL'). Coverage: 3,153 counties. It is categorised as a Read tool in the AlpineDataWorks Intelligence Server MCP Server, which means it retrieves data without modifying state.
adw.county_mortality accepts 1 parameter: county. Required: county. The full parameter table on this page comes from the server's own tool schema.
Register the AlpineDataWorks Intelligence Server MCP server in PolicyLayer and add a rule for adw.county_mortality: 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 AlpineDataWorks Intelligence Server. Nothing to install.
adw.county_mortality 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 adw.county_mortality 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 adw.county_mortality. 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.
adw.county_mortality is provided by the AlpineDataWorks Intelligence Server MCP server (https://api.alpinedataworks.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AlpineDataWorks Intelligence Server, and thousands of servers like it.
Across the catalogue