Low Risk

cdc_query_dataset

Execute a SoQL query against any CDC dataset. Supports filtering, aggregation, sorting, full-text search, and field selection. Use cdc_discover_datasets to find dataset IDs and cdc_get_dataset_schema to inspect columns before querying.

Part of the Cdc Health server.

cdc_query_dataset is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CDC HEALTH →

Free to start. No card required.

AI agents call cdc_query_dataset to retrieve information from Cdc Health without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though cdc_query_dataset only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cdc_query_dataset": {}
  }
}

See the full Cdc Health policy for all 3 tools.

Get this rule live on your own Cdc Health server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CDC HEALTH →

These attack patterns abuse exactly the kind of access cdc_query_dataset gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cdc_query_dataset only ever does what you allow.

SECURE CDC HEALTH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the cdc_query_dataset tool do? +

Execute a SoQL query against any CDC dataset. Supports filtering, aggregation, sorting, full-text search, and field selection. Use cdc_discover_datasets to find dataset IDs and cdc_get_dataset_schema to inspect columns before querying.. It is categorised as a Read tool in the Cdc Health MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cdc_query_dataset? +

Register the Cdc Health MCP server in PolicyLayer and add a rule for cdc_query_dataset: 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 Cdc Health. Nothing to install.

What risk level is cdc_query_dataset? +

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

Can I rate-limit cdc_query_dataset? +

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

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

cdc_query_dataset is provided by the Cdc Health MCP server (cyanheads/cdc-health-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cdc Health tool call.

Deterministic rules across all 3 Cdc Health tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.