Aggregate order revenue grouped by day/week/month within a date range. Returns groups with total_revenue (VND), order_count, avg_order_value plus overall totals.
AI agents call revenue_summary to retrieve information from Sapo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and aggregates existing financial data for reporting purposes. It performs no writes, deletes, or external execution. While it deals with financial information, it does not move money, commit obligations, or change account states—it simply reads and summarizes order history.
From the tool's definition Tool retrieves and aggregates order revenue data ("Aggregate order revenue grouped by day/week/month") and returns summaries with totals.
Documented attack patterns abuse exactly the kind of access revenue_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sapo, and nothing reaches the server without passing your rules. This is the rule we recommend for revenue_summary:
{
"version": "1",
"default": "deny",
"tools": {
"revenue_summary": {}
}
}revenue_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Aggregate order revenue grouped by day/week/month within a date range. Returns groups with total_revenue (VND), order_count, avg_order_value plus overall totals. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.
Register the Sapo MCP server in PolicyLayer and add a rule for revenue_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 Sapo. Nothing to install.
revenue_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 revenue_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 revenue_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.
revenue_summary is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sapo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Sapo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.