run_all_safety_checks
Runs ALL 8 safety checks (drug interactions, allergy, disease, age, renal, pregnancy, duplicate therapy, and AYUSH herb-drug) in a single call. Returns pre-formatted check results array ready to pass directly to aggregate_risk_score. Use this instead of calling individual check tools separately.
This record as markdown: /tools/nitrostack/run-all-safety-checks.md
What run_all_safety_checks does on Nitrostack
AI agents invoke run_all_safety_checks to trigger actions in Nitrostack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_all_safety_checks is rated High
Executes complex medical safety validation logic affecting downstream risk aggregation decisions with significant health impact.
From the tool's definition Runs ALL 8 safety checks in single call, returns formatted results array
Attacks that exploit this kind of access
The rule that runs run_all_safety_checks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_all_safety_checks, this is the rule to start with:
run_all_safety_checks stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every run_all_safety_checks call is checked against it from then on.
Questions about run_all_safety_checks
Runs ALL 8 safety checks (drug interactions, allergy, disease, age, renal, pregnancy, duplicate therapy, and AYUSH herb-drug) in a single call. Returns pre-formatted check results array ready to pass directly to aggregate_risk_score. Use this instead of calling individual check tools separately. It is categorised as a Execute tool in the Nitrostack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nitrostack MCP server in PolicyLayer and add a rule for run_all_safety_checks: 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 Nitrostack. Nothing to install.
run_all_safety_checks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_all_safety_checks 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 run_all_safety_checks. 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.
run_all_safety_checks is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue