report_dashboard
Executive summary of the organization: today's sessions, monthly metrics, revenue, pending charges, and alerts.
This record as markdown: /tools/com-servicialo-mcp-server/report-dashboard.md
What report_dashboard does on Servicialo
AI agents call report_dashboard 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 |
|---|---|---|---|
date | string | — | |
apiKey | string | — | |
orgSlug | string | Yes |
Parameters from the server's own tool schema.
Why report_dashboard is rated Low
This tool queries organizational metrics and reports summaries without modifying, creating, destroying, or executing operations. While it may access sensitive business data (revenue, charges), the core capability is data retrieval and presentation, which is characteristic of a Read operation. The lack of any side effects keeps severity low despite access to financial summaries.
From the tool's definition Tool name 'report_dashboard' and description indicate it retrieves and summarizes data: 'Executive summary...today's sessions, monthly metrics, revenue, pending charges, and alerts.' No verbs like create, update, delete, execute, or modify are mentioned; it…
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs report_dashboard 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_dashboard, this is the rule to start with:
report_dashboard 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_dashboard call is checked against it from then on.
Questions about report_dashboard
Executive summary of the organization: today's sessions, monthly metrics, revenue, pending charges, and alerts. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
report_dashboard accepts 3 parameters: date, apiKey, orgSlug. 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_dashboard: 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_dashboard 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_dashboard 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_dashboard. 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_dashboard 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