session_note_get
Read the clinical note of a session. Non-restricted notes return full content. Notes marked dataSensitivity=restricted return metadata only (type, sensitivity, timestamps, which fields are present) with the clinical text withheld — pass includeRestricted: true to retrieve the full content, which ...
This record as markdown: /tools/com-servicialo-mcp-server/session-note-get.md
What session_note_get does on Servicialo
AI agents call session_note_get to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
sessionId | string | Yes | |
includeRestricted | boolean | — |
Parameters from the server's own tool schema.
Why session_note_get is rated Low
This is a Read operation—it retrieves sensitive clinical data without altering it. However, severity is high rather than low/medium because: (1) the data accessed is clinical/health information (PHI-equivalent), (2) unrestricted access to full content is available, and (3) misuse by an AI agent could expose sensitive patient records at scale.
From the tool's definition Tool description explicitly states it 'Read[s] the clinical note of a session' and 'return[s]' note content. Primary function is data retrieval with no modification or deletion.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs session_note_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session_note_get, this is the rule to start with:
session_note_get 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 Servicialo, apply this rule, and every session_note_get call is checked against it from then on.
Questions about session_note_get
Read the clinical note of a session. Non-restricted notes return full content. Notes marked dataSensitivity=restricted return metadata only (type, sensitivity, timestamps, which fields are present) with the clinical text withheld — pass includeRestricted: true to retrieve the full content, which logs an audited restricted-access event and increments the access counter. Returns note: null if the session has no note. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
session_note_get accepts 4 parameters: apiKey, orgSlug, sessionId, includeRestricted. Required: orgSlug, sessionId. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for session_note_get: 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 Servicialo. Nothing to install.
session_note_get 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 session_note_get 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 session_note_get. 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.
session_note_get is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue