portal_session_confirm

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 32 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/portal-session-confirm.md

WHAT IT DOES

What portal_session_confirm does on Servicialo

AI agents use portal_session_confirm 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
`apiKey`	string	—
`orgSlug`	string	Yes
`sessionId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why portal_session_confirm is rated Medium

This tool updates the status of a session from scheduled/pending_confirmation to confirmed and triggers a notification to the provider. It modifies existing data in a reversible way (status change), which fits the Write category. It does not delete data, execute code, or involve financial transactions.

From the tool's definition Confirm a client's attendance to their session... Moves scheduled/pending_confirmation → confirmed and notifies the provider. Idempotent: a session already confirmed returns alreadyConfirmed=true.

Risk signalsHandles credentials or secrets (apiKey) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

portal_session_confirm Rate-limited

portal_session_confirm 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": {
    "portal_session_confirm": {
      "limits": [
        {
          "counter": "portal_session_confirm_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 portal_session_confirm call is checked against it from then on.

FAQ

Questions about portal_session_confirm

What does the portal_session_confirm tool do? +

Confirm a client's attendance to their session, on behalf of the client (e.g. the client called or messaged the org to confirm). Moves scheduled/pending_confirmation → confirmed and notifies the provider. This is the client-portal confirm flow (event role = client), distinct from the org's own admin confirm in booking_update_status. Idempotent: a session already confirmed returns alreadyConfirmed=true. The org API key owner is recorded as the actor acting on behalf of the client (ADR-004 §6). 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 portal_session_confirm accept? +

portal_session_confirm accepts 3 parameters: apiKey, orgSlug, sessionId. 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 portal_session_confirm? +

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

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

Can I rate-limit portal_session_confirm? +

Yes. Add a rate_limit block to the portal_session_confirm 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 portal_session_confirm completely? +

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

portal_session_confirm 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 →