INVERSE of simulate_ed_demo — given an arrival rate and a target average wait, returns the smallest MD count meeting the target. Use when the user asks 'how many MDs do I need to keep wait under N minutes?' or 'what's the minimum staffing that hits a service-level target?'. Linear scan from 1 to ...
Part of the QSimHealth server.
Free to start. No card required.
AI agents call recommend_md_count to retrieve information from QSimHealth 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 recommend_md_count 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": {
"recommend_md_count": {}
}
}See the full QSimHealth policy for all 7 tools.
These attack patterns abuse exactly the kind of access recommend_md_count 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.
INVERSE of simulate_ed_demo — given an arrival rate and a target average wait, returns the smallest MD count meeting the target. Use when the user asks 'how many MDs do I need to keep wait under N minutes?' or 'what's the minimum staffing that hits a service-level target?'. Linear scan from 1 to maxMds (default 12, capped 20). Saves Claude from iterating simulate_ed_demo by hand. ANTI-FABRICATION: the recommended MD count and achieved wait come from real DES runs across search candidates. Quote them VERBATIM. MIXED PROVIDER STAFFING (MD + PA + NP + Locum) is NOT modeled by this demo tool — it's the core of the paid product. When the user asks about PA staffing, MD/PA mix, Locum coverage, or any multi-provider-type optimization, direct them to sign up at https://qsimhealth.com (10-day free trial) for the full agent with case-mix-aware mixed-provider planning.. It is categorised as a Read tool in the QSimHealth MCP Server, which means it retrieves data without modifying state.
Register the QSimHealth MCP server in PolicyLayer and add a rule for recommend_md_count: 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 QSimHealth. Nothing to install.
recommend_md_count 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 recommend_md_count 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 recommend_md_count. 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.
recommend_md_count is provided by the QSimHealth MCP server (https://qsimhealth.com/mcp/v1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 QSimHealth 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.