ingest_patient_record
Upload a patient record file (.txt, .csv, .pdf, .docx) or paste unstructured clinical text to extract a structured patient profile. The file is decoded, text is extracted, and Gemini LLM converts it into the same JSON format used by all PharmaGuard safety tools. The patient is stored in memory wi...
This record as markdown: /tools/nitrostack/ingest-patient-record.md
What ingest_patient_record does on Nitrostack
AI agents use ingest_patient_record to create or update resources in Nitrostack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nitrostack environment.
Why ingest_patient_record is rated Medium
Creates and stores patient records in system memory; reversible write with high sensitivity given medical data involved.
From the tool's definition Upload patient record file, extract structured patient profile, patient stored in memory
Attacks that exploit this kind of access
The rule that runs ingest_patient_record 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 ingest_patient_record, this is the rule to start with:
ingest_patient_record stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 ingest_patient_record call is checked against it from then on.
Questions about ingest_patient_record
Upload a patient record file (.txt, .csv, .pdf, .docx) or paste unstructured clinical text to extract a structured patient profile. The file is decoded, text is extracted, and Gemini LLM converts it into the same JSON format used by all PharmaGuard safety tools. The patient is stored in memory with an assigned ID for immediate use in safety checks. Supported formats: plain text, CSV, PDF (text-based), DOCX. It is categorised as a Write tool in the Nitrostack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nitrostack MCP server in PolicyLayer and add a rule for ingest_patient_record: 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.
ingest_patient_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ingest_patient_record 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 ingest_patient_record. 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.
ingest_patient_record 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