cdc_dataset_query
Generic SoQL query against any data.cdc.gov dataset. Use this when none of the curated tools fit. Accepts a 4x4 Socrata ID and a where-clause. SoQL reference: https://dev.socrata.com/docs/queries/
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cdc-dataset-query.md
What cdc_dataset_query does on Livedatalink
AI agents invoke cdc_dataset_query to trigger actions in Livedatalink. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max rows (default 50) |
order | string | — | SoQL order clause (e.g. 'date DESC') |
where | string | — | SoQL where clause (e.g. "state='Texas' AND year=2024") |
select | string | — | SoQL select clause (default '*') |
dataset | string | Yes | Socrata 4x4 dataset ID (e.g. 'muzy-jte6') |
Parameters from the server's own tool schema.
Why cdc_dataset_query is rated High
This tool executes arbitrary SoQL queries against CDC's Socrata platform. While CDC's public data portal is read-only for external users, the tool accepts user-supplied query logic (where-clause) that is executed against an external system, placing it in Execute rather than Read.
From the tool's definition 'Generic SoQL query against any data.cdc.gov dataset' and 'Accepts a 4x4 Socrata ID and a where-clause' — executes arbitrary SoQL queries against an external data platform
Attacks that exploit this kind of access
The rule that runs cdc_dataset_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdc_dataset_query, this is the rule to start with:
cdc_dataset_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every cdc_dataset_query call is checked against it from then on.
Questions about cdc_dataset_query
Generic SoQL query against any data.cdc.gov dataset. Use this when none of the curated tools fit. Accepts a 4x4 Socrata ID and a where-clause. SoQL reference: https://dev.socrata.com/docs/queries/. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
cdc_dataset_query accepts 5 parameters: limit, order, where, select, dataset. Required: dataset. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for cdc_dataset_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 Livedatalink. Nothing to install.
cdc_dataset_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cdc_dataset_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_dataset_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_dataset_query is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
Across the catalogue