Low Risk

get_medicare_enrollment

Get Medicare enrollment data by state and county. Returns enrollment counts including total beneficiaries, Original Medicare vs Medicare Advantage enrollment, and Part D enrollment. Useful for understanding Medicare population by geography. Args: state: Two-letter US state abbreviation (e.g. 'CA'...

Part of the CMS Medicare Data server.

get_medicare_enrollment 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 CMS MEDICARE DATA →

Free to start. No card required.

AI agents call get_medicare_enrollment 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_medicare_enrollment 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_medicare_enrollment": {}
  }
}

See the full CMS Medicare Data policy for all 5 tools.

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

ENFORCE ON MY CMS MEDICARE DATA →

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

SECURE CMS MEDICARE 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_medicare_enrollment tool do? +

Get Medicare enrollment data by state and county. Returns enrollment counts including total beneficiaries, Original Medicare vs Medicare Advantage enrollment, and Part D enrollment. Useful for understanding Medicare population by geography. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). year: Year of enrollment 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.

How do I enforce a policy on get_medicare_enrollment? +

Register the CMS Medicare Data MCP server in PolicyLayer and add a rule for get_medicare_enrollment: 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.

What risk level is get_medicare_enrollment? +

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

Can I rate-limit get_medicare_enrollment? +

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

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

get_medicare_enrollment 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.

Enforce policy on every CMS Medicare Data tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.