cdc.health.query
Query a specific CDC dataset using SoQL filters — filter by state, year, age group, condition. Returns structured rows with column names. Supports WHERE, SELECT, ORDER, GROUP BY. Use cdc.datasets to find dataset IDs first (US Gov, Socrata SODA API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cdc.health.query.md
What cdc.health.query does on Apibase
AI agents call cdc.health.query to retrieve information from Apibase 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 |
|---|---|---|---|
group | string | — | Group by columns for aggregation (e.g. "state" with select "state, SUM(deaths)") |
limit | integer | — | Max rows to return (1-1000, default 100) |
order | string | — | Sort order (e.g. "year DESC", "deaths DESC"). Default: dataset default order. |
where | string | — | SoQL WHERE clause filter (e.g. "state='CA'", "year > 2020", "age_group='65+'") |
select | string | — | Columns to return, comma-separated (e.g. "state, year, deaths"). Default: all columns. |
dataset_id | string | Yes | CDC dataset ID in xxxx-xxxx format (e.g. "9bhg-hcku" for COVID deaths). Use cdc.datasets to find IDs. |
Parameters from the server's own tool schema.
Why cdc.health.query is rated Low
Tool retrieves and filters public health data without modification or execution permissions.
From the tool's definition Query a specific CDC dataset using SoQL filters. Returns structured rows.
Attacks that exploit this kind of access
The rule that runs cdc.health.query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdc.health.query, this is the rule to start with:
cdc.health.query 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 Apibase, apply this rule, and every cdc.health.query call is checked against it from then on.
Questions about cdc.health.query
Query a specific CDC dataset using SoQL filters — filter by state, year, age group, condition. Returns structured rows with column names. Supports WHERE, SELECT, ORDER, GROUP BY. Use cdc.datasets to find dataset IDs first (US Gov, Socrata SODA API). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cdc.health.query accepts 6 parameters: group, limit, order, where, select, dataset_id. Required: dataset_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for cdc.health.query: 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 Apibase. Nothing to install.
cdc.health.query 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.health.query 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.health.query. 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.health.query is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue