[UNDOCUMENTED endpoint, verified 2026-04-30, schema may change] Shift summary: orders count, total revenue, breakdown by payment method. Cashbook NOT included (internal-only endpoint).
AI agents call shift_report 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 queries and returns aggregated reporting data (orders count, revenue, payment method breakdown) without modifying any records or triggering external actions. It is a read-only retrieval operation with no side effects. The 'low' severity reflects that misuse would expose business metrics but cannot directly harm data or trigger irreversible actions.
From the tool's definition Tool retrieves shift summary data: 'orders count, total revenue, breakdown by payment method.' No modifications, deletions, or external operations are performed.
Documented attack patterns abuse exactly the kind of access shift_report 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 shift_report:
{
"version": "1",
"default": "deny",
"tools": {
"shift_report": {}
}
}shift_report 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.
[UNDOCUMENTED endpoint, verified 2026-04-30, schema may change] Shift summary: orders count, total revenue, breakdown by payment method. Cashbook NOT included (internal-only endpoint). 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 shift_report: 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.
shift_report 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 shift_report 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 shift_report. 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.
shift_report 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.