report_sc_summary
Breakdown of Servicio Coordinado (SC) events by month and resolver path (backfill, cac-native, live, compensalo). Use to validate SC coverage and monitor live SC resolution growth. Key metric: sc_live shows SCs resolved in production (not backfill).
This record as markdown: /tools/com-servicialo-mcp-server/report-sc-summary.md
What report_sc_summary does on Servicialo
AI agents call report_sc_summary 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 | |
periodo | string | — |
Parameters from the server's own tool schema.
Why report_sc_summary is rated Low
This is a read-only reporting tool that retrieves and summarizes existing Servicio Coordinado event data. It has no side effects, does not modify or delete data, and does not execute external operations. The blast radius of misuse is minimal—an agent could only access summary metrics about service events. Low severity is appropriate for passive data retrieval in a service delivery context.
From the tool's definition report_sc_summary retrieves and breaks down service coordination events by month and resolver path. The description explicitly indicates it is used to 'validate' and 'monitor' metrics, with no mention of modification, deletion, or execution capabilities.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs report_sc_summary 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 report_sc_summary, this is the rule to start with:
report_sc_summary 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 report_sc_summary call is checked against it from then on.
Questions about report_sc_summary
Breakdown of Servicio Coordinado (SC) events by month and resolver path (backfill, cac-native, live, compensalo). Use to validate SC coverage and monitor live SC resolution growth. Key metric: sc_live shows SCs resolved in production (not backfill). It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
report_sc_summary accepts 3 parameters: apiKey, orgSlug, periodo. Required: orgSlug. 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 report_sc_summary: 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.
report_sc_summary 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 report_sc_summary 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 report_sc_summary. 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.
report_sc_summary 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