report_revenue_summary
Generate a revenue summary report for a date range. Aggregates orders by status and splits paid vs. unpaid revenue. Capped at 100 orders — use a tighter date range for high-volume shops.
This record as markdown: /tools/abbottdevelopments-shopmonkey-mcp-server/report-revenue-summary.md
What report_revenue_summary does on Shopmonkey MCP Server
AI agents call report_revenue_summary to retrieve information from Shopmonkey MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why report_revenue_summary is rated Low
This tool retrieves and summarizes existing financial data (revenue by status and payment state) without creating, modifying, deleting, or moving money. It is a reporting/analytics function that generates insights from historical data. The low severity reflects minimal blast radius: an AI agent misusing this tool could only access financial visibility data, not alter transactions, payments, or business state.
From the tool's definition Tool name 'report_revenue_summary' and description 'Generate a revenue summary report' indicate data retrieval and aggregation.
Attacks that exploit this kind of access
The rule that runs report_revenue_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Shopmonkey MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For report_revenue_summary, this is the rule to start with:
report_revenue_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 Shopmonkey MCP Server, apply this rule, and every report_revenue_summary call is checked against it from then on.
Questions about report_revenue_summary
Generate a revenue summary report for a date range. Aggregates orders by status and splits paid vs. unpaid revenue. Capped at 100 orders — use a tighter date range for high-volume shops. It is categorised as a Read tool in the Shopmonkey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shopmonkey MCP Server MCP server in PolicyLayer and add a rule for report_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 Shopmonkey MCP Server. Nothing to install.
report_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 report_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 report_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.
report_revenue_summary is provided by the Shopmonkey MCP Server MCP server (abbottdevelopments/shopmonkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Shopmonkey MCP Server, and thousands of servers like it.
This server
Across the catalogue