health.medicare-provider
Medicare utilization + payments by provider (CMS annual dataset): beneficiary counts, total services, submitted charges, Medicare payment amounts per NPI. By npi, or lastName + state. Pairs with health.open-payments.
This record as markdown: /tools/io-github-2s-io-mcp/health.medicare-provider.md
What health.medicare-provider does on Mcp
AI agents call health.medicare-provider to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health.medicare-provider is rated Low
The tool performs data retrieval and querying of historical Medicare payment information. It is a read-only query against public CMS datasets with no side effects, no ability to modify records, and no financial transactions. The data returned is informational aggregate statistics. Confidence is high because the description clearly indicates query/retrieval semantics ('utilization + payments...
From the tool's definition Tool retrieves Medicare utilization and payment data (beneficiary counts, services, charges, payments) by querying CMS datasets using NPI or provider name/state. No modification, deletion, or financial transaction capability described.
Attacks that exploit this kind of access
The rule that runs health.medicare-provider safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health.medicare-provider, this is the rule to start with:
health.medicare-provider is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every health.medicare-provider call is checked against it from then on.
Questions about health.medicare-provider
Medicare utilization + payments by provider (CMS annual dataset): beneficiary counts, total services, submitted charges, Medicare payment amounts per NPI. By npi, or lastName + state. Pairs with health.open-payments. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for health.medicare-provider: 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 Mcp. Nothing to install.
health.medicare-provider 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 health.medicare-provider 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 health.medicare-provider. 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.
health.medicare-provider is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue