report_revenue
Calculate revenue for a period grouped by day, week, month, service, or provider.
This record as markdown: /tools/com-servicialo-mcp-server/report-revenue.md
What report_revenue does on Servicialo
AI agents call report_revenue 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 | — | |
dateTo | string | — | |
groupBy | string | — | |
orgSlug | string | Yes | |
dateFrom | string | — |
Parameters from the server's own tool schema.
Why report_revenue is rated Low
This tool retrieves and calculates financial data for reporting purposes without modifying, deleting, or moving any money. It is a passive aggregation/analysis function that produces summaries from existing financial records. While it accesses financial data, it does not constitute a Financial category risk (which requires actual money movement or commitment).
From the tool's definition Tool name 'report_revenue' and description 'Calculate revenue for a period grouped by day, week, month, service, or provider' indicate a read-only reporting and querying operation.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs report_revenue 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_revenue, this is the rule to start with:
report_revenue 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_revenue call is checked against it from then on.
Questions about report_revenue
Calculate revenue for a period grouped by day, week, month, service, or provider. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
report_revenue accepts 5 parameters: apiKey, dateTo, groupBy, orgSlug, dateFrom. 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_revenue: 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_revenue 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_revenue 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_revenue. 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_revenue 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