session_note_upsert

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 92 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/session-note-upsert.md

WHAT IT DOES

What session_note_upsert does on Servicialo

AI agents use session_note_upsert to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.

Parameter	Type	Required
`type`	object	—
`apiKey`	string	—
`orgSlug`	string	Yes
`evolution`	object	—
`isPrivate`	boolean	—
`sessionId`	string	Yes
`dataSensitivity`	string	—
`nextSessionPlan`	object	—
`treatmentPerformed`	object	—

Parameters from the server's own tool schema.

RISK

Why session_note_upsert is rated Medium

The tool creates or modifies health records (clinical notes, session metadata, progress metrics) via an upsert operation. This is reversible (update/overwrite possible) rather than irreversible deletion, placing it in Write.

From the tool's definition Create or update the clinical note (ficha) of a session: evolution, treatmentPerformed, nextSessionPlan, type, progressMetrics, etc. One note per session (upsert).

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_note_upsert 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_upsert, this is the rule to start with:

session_note_upsert Rate-limited

session_note_upsert 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session_note_upsert": {
      "limits": [
        {
          "counter": "session_note_upsert_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every session_note_upsert call is checked against it from then on.

FAQ

Questions about session_note_upsert

What does the session_note_upsert tool do? +

Create or update the clinical note (ficha) of a session: evolution, treatmentPerformed, nextSessionPlan, type (evaluacion/tratamiento/derivacion/cierre), progressMetrics, etc. One note per session (upsert). Sensitivity is resolved automatically (health-vertical orgs default to restricted). NOTE: unlike the provider's own UI save, this does NOT create the provider-confirmed DeliveryProof nor award practice points — those are provider-bound actions (PDC-SEC-001); use the provider portal / REST for delivery confirmation. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does session_note_upsert accept? +

session_note_upsert accepts 9 parameters: type, apiKey, orgSlug, evolution, isPrivate, sessionId, dataSensitivity, nextSessionPlan, treatmentPerformed. Required: orgSlug, sessionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on session_note_upsert? +

Register the Servicialo MCP server in PolicyLayer and add a rule for session_note_upsert: 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.

What risk level is session_note_upsert? +

session_note_upsert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit session_note_upsert? +

Yes. Add a rate_limit block to the session_note_upsert 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.

How do I block session_note_upsert completely? +

Set action: deny in the PolicyLayer policy for session_note_upsert. 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.

What MCP server provides session_note_upsert? +

session_note_upsert 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.

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →