Get prevalence of chronic conditions among Medicare beneficiaries. Returns state-level data on 21 chronic conditions including diabetes, heart failure, COPD, depression, Alzheimer's, and more. Useful for understanding disease burden by geography. Args: state: Two-letter US state abbreviation (e.g...
Part of the CMS Medicare Data server.
Free to start. No card required.
AI agents call get_chronic_conditions to retrieve information from CMS Medicare 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_chronic_conditions 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_chronic_conditions": {}
}
}See the full CMS Medicare Data policy for all 5 tools.
These attack patterns abuse exactly the kind of access get_chronic_conditions gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get prevalence of chronic conditions among Medicare beneficiaries. Returns state-level data on 21 chronic conditions including diabetes, heart failure, COPD, depression, Alzheimer's, and more. Useful for understanding disease burden by geography. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). condition: Chronic condition name to filter by (e.g. 'diabetes', 'heart failure', 'COPD', 'depression'). year: Year of data (e.g. 2022). limit: Maximum number of records to return (default 50, max 1000).. It is categorised as a Read tool in the CMS Medicare Data MCP Server, which means it retrieves data without modifying state.
Register the CMS Medicare Data MCP server in PolicyLayer and add a rule for get_chronic_conditions: 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 CMS Medicare Data. Nothing to install.
get_chronic_conditions 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 get_chronic_conditions 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 get_chronic_conditions. 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.
get_chronic_conditions is provided by the CMS Medicare Data MCP server (https://mcp.olyport.com/cms-medicare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 CMS Medicare 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.