Low Risk

get_measure_by_state

Get one CDC PLACES measure for all counties in a state. Useful for comparing a specific health metric (e.g. DIABETES, OBESITY) across all counties within a state. Returns the most recent data year. Args: state_abbr: Two-letter state abbreviation (e.g. 'WA', 'CA'). measure_id: PLACES measure ID (e...

Part of the CDC PLACES Health Data server.

get_measure_by_state 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 PLACES HEALTH DATA →

Free to start. No card required.

AI agents call get_measure_by_state to retrieve information from CDC PLACES Health Data 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 get_measure_by_state 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": {
    "get_measure_by_state": {}
  }
}

See the full CDC PLACES Health Data policy for all 5 tools.

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

ENFORCE ON MY CDC PLACES HEALTH DATA →

These attack patterns abuse exactly the kind of access get_measure_by_state 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 get_measure_by_state only ever does what you allow.

SECURE CDC PLACES HEALTH DATA →

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

What does the get_measure_by_state tool do? +

Get one CDC PLACES measure for all counties in a state. Useful for comparing a specific health metric (e.g. DIABETES, OBESITY) across all counties within a state. Returns the most recent data year. Args: state_abbr: Two-letter state abbreviation (e.g. 'WA', 'CA'). measure_id: PLACES measure ID (e.g. 'DIABETES', 'OBESITY', 'BPHIGH'). Use search_measures to find valid IDs.. It is categorised as a Read tool in the CDC PLACES Health Data MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_measure_by_state? +

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

What risk level is get_measure_by_state? +

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

Can I rate-limit get_measure_by_state? +

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

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

get_measure_by_state is provided by the CDC PLACES Health Data MCP server (https://mcp.olyport.com/cdc-places/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CDC PLACES Health Data tool call.

Deterministic rules across all 5 CDC PLACES Health Data 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.