List orders created at the POS counter (source_name=pos). For cashiers — review in-store sales. Returns paginated results via since_id cursor.
AI agents call list_pos_orders 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.
The tool retrieves and queries existing POS orders for review purposes. It has no side effects, does not execute commands, does not modify or delete data, and does not involve financial transactions. This is a straightforward Read operation appropriate for cashier visibility into in-store sales.
From the tool's definition Tool description states 'List orders' and 'review in-store sales' with 'paginated results via since_id cursor' — a retrieval operation with no data modification.
Documented attack patterns abuse exactly the kind of access list_pos_orders 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 list_pos_orders:
{
"version": "1",
"default": "deny",
"tools": {
"list_pos_orders": {}
}
}list_pos_orders 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.
List orders created at the POS counter (source_name=pos). For cashiers — review in-store sales. Returns paginated results via since_id cursor. 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 list_pos_orders: 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.
list_pos_orders 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 list_pos_orders 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 list_pos_orders. 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.
list_pos_orders 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.