triage_symptoms
Classify free-form emergency symptom text into a severity level (Critical/Severe/Moderate/Mild) and the hospital department/specialization required, using a deterministic rule-based classifier.
This record as markdown: /tools/nitrostack/triage-symptoms.md
What triage_symptoms does on Nitrostack
AI agents call triage_symptoms to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why triage_symptoms is rated Low
Tool analyzes symptoms to produce clinical classification without modifying patient data or triggering external systems.
From the tool's definition Classify free-form text into severity level and department, deterministic rule-based classifier.
Attacks that exploit this kind of access
The rule that runs triage_symptoms 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 triage_symptoms, this is the rule to start with:
triage_symptoms 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 Nitrostack, apply this rule, and every triage_symptoms call is checked against it from then on.
Questions about triage_symptoms
Classify free-form emergency symptom text into a severity level (Critical/Severe/Moderate/Mild) and the hospital department/specialization required, using a deterministic rule-based classifier. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.
Register the Nitrostack MCP server in PolicyLayer and add a rule for triage_symptoms: 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.
triage_symptoms 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 triage_symptoms 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 triage_symptoms. 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.
triage_symptoms 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.
This server
Across the catalogue