health.mortality-stats

US mortality statistics (CDC NCHS). dataset=leading-causes: annual deaths + age-adjusted rate by state and top-10 cause, 1999-2017. dataset=weekly-counts: provisional weekly deaths by jurisdiction + cause, 2020-2023.

Server Mcp @2sio/mcp
Category Read
Risk class Low
Parameters 00 required

What health.mortality-stats does on Mcp

AI agents call health.mortality-stats to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why health.mortality-stats needs a policy

This tool performs read-only data retrieval from public health datasets. It has no side effects, cannot modify or delete data, does not execute code or commands, and involves no financial transactions. The worst-case misuse scenario (querying for mortality statistics to inform inappropriate analysis) poses minimal direct harm and is a low-severity risk.

From the tool's definition Tool retrieves and queries US mortality statistics from CDC NCHS datasets. Descriptors 'annual deaths', 'by state', 'by jurisdiction', and 'by cause' indicate data retrieval operations.

Questions about health.mortality-stats

What does the health.mortality-stats tool do? +

US mortality statistics (CDC NCHS). dataset=leading-causes: annual deaths + age-adjusted rate by state and top-10 cause, 1999-2017. dataset=weekly-counts: provisional weekly deaths by jurisdiction + cause, 2020-2023. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health.mortality-stats? +

Register the MCP server in PolicyLayer and add a rule for health.mortality-stats: 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 Mcp. Nothing to install.

What risk level is health.mortality-stats? +

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

Can I rate-limit health.mortality-stats? +

Yes. Add a rate_limit block to the health.mortality-stats 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 health.mortality-stats completely? +

Set action: deny in the PolicyLayer policy for health.mortality-stats. 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 health.mortality-stats? +

health.mortality-stats is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.