cdc_chronic.disease.topics
List all available chronic disease topics and their associated indicator questions in the CDC CDI dataset. Returns topic IDs (e.g. DIA=Diabetes, CVD=Cardiovascular, TOB=Tobacco) and question IDs (e.g. DIA01=Diabetes prevalence, TOB04=Cigarette smoking, CVD01=High blood pressure) needed for other ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cdc-chronic.disease.topics.md
What cdc_chronic.disease.topics does on Apibase
AI agents call cdc_chronic.disease.topics 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 |
|---|---|---|---|
topic_id | string | — | Filter by a single topic to see only its questions. Omit to list all 19 topics with their questions. Options: ALC=Alcohol, ART=Arthritis, AST=Asthma, CAN=Cancer |
Parameters from the server's own tool schema.
Why cdc_chronic.disease.topics is rated Low
Tool queries and lists public CDC disease metadata with no side effects, modifications, or external operations.
From the tool's definition List all available chronic disease topics and indicator questions. Returns topic IDs and question IDs.
Attacks that exploit this kind of access
The rule that runs cdc_chronic.disease.topics 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_chronic.disease.topics, this is the rule to start with:
cdc_chronic.disease.topics 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_chronic.disease.topics call is checked against it from then on.
Questions about cdc_chronic.disease.topics
List all available chronic disease topics and their associated indicator questions in the CDC CDI dataset. Returns topic IDs (e.g. DIA=Diabetes, CVD=Cardiovascular, TOB=Tobacco) and question IDs (e.g. DIA01=Diabetes prevalence, TOB04=Cigarette smoking, CVD01=High blood pressure) needed for other cdc_chronic tools. Optionally filter to a single topic. 19 topics, 100+ indicator questions. Source: CDC CDI Socrata dataset hksd-2xuw. No auth — US Gov public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cdc_chronic.disease.topics accepts 1 parameter: topic_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_chronic.disease.topics: 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_chronic.disease.topics 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_chronic.disease.topics 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_chronic.disease.topics. 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_chronic.disease.topics 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