doctor_intake
Interactive patient intake: asks four mandatory questions, returns a structured intake summary, and offers appointment recommendations without diagnosing or prescribing medicines.
This record as markdown: /tools/nitrostack/doctor-intake.md
What doctor_intake does on Nitrostack
AI agents call doctor_intake 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 doctor_intake is rated Low
Gathers patient information and recommendations; no data modification, execution, or clinical treatment.
From the tool's definition asks questions, returns structured intake summary, no diagnosing or prescribing
Attacks that exploit this kind of access
The rule that runs doctor_intake 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 doctor_intake, this is the rule to start with:
doctor_intake 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 doctor_intake call is checked against it from then on.
Questions about doctor_intake
Interactive patient intake: asks four mandatory questions, returns a structured intake summary, and offers appointment recommendations without diagnosing or prescribing medicines. 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 doctor_intake: 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.
doctor_intake 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 doctor_intake 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 doctor_intake. 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.
doctor_intake 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