Check if someone qualifies for ACA Marketplace health insurance subsidies in 2026. Provide household size (number of people) and estimated annual household income in dollars.
Part of the Healthcovered Mcp server.
Free to start. No card required.
AI agents call check_aca_eligibility to retrieve information from Healthcovered Mcp 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 check_aca_eligibility 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": {
"check_aca_eligibility": {}
}
}See the full Healthcovered Mcp policy for all 3 tools.
These attack patterns abuse exactly the kind of access check_aca_eligibility 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.
Check if someone qualifies for ACA Marketplace health insurance subsidies in 2026. Provide household size (number of people) and estimated annual household income in dollars.. It is categorised as a Read tool in the Healthcovered Mcp MCP Server, which means it retrieves data without modifying state.
Register the Healthcovered MCP server in PolicyLayer and add a rule for check_aca_eligibility: 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 Healthcovered Mcp. Nothing to install.
check_aca_eligibility 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 check_aca_eligibility 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 check_aca_eligibility. 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.
check_aca_eligibility is provided by the Healthcovered MCP server (https://healthcovered-mcp.onrender.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Healthcovered Mcp 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.