portal_report_session

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 53 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-report-session.md

WHAT IT DOES

What portal_report_session does on Servicialo

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

Parameters from the server's own tool schema.

RISK

Why portal_report_session is rated Medium

The tool creates a new dispute record (a Write operation) and sends a notification to the org. It is reversible in the sense that it opens a dispute for review rather than making irreversible changes. While it could indirectly lead to financial consequences (e.g., refunds after dispute resolution), the tool itself does not move money or commit financial obligations — it only initiates a review process.

From the tool's definition Creates a Dispute(OPEN) for the org to review — it does NOT change the session status. Idempotent: if an open dispute already exists for the session, returns alreadyReported=true with its disputeId. Notifies the org.

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

portal_report_session Rate-limited

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

FAQ

Questions about portal_report_session

What does the portal_report_session tool do? +

Report, on behalf of the client, that the professional did not show up (reason=provider_no_show) or that the session was cancelled/not delivered (reason=cancelled). Creates a Dispute(OPEN) for the org to review — it does NOT change the session status. Idempotent: if an open dispute already exists for the session, returns alreadyReported=true with its disputeId. Notifies the org. 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_report_session accept? +

portal_report_session accepts 5 parameters: note, apiKey, reason, orgSlug, sessionId. Required: reason, 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_report_session? +

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

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

Can I rate-limit portal_report_session? +

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

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

portal_report_session 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

generate_devtools_report on Percepta MCP Server →generate_forensic_report on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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