[UNDOCUMENTED endpoint, verified 2026-04-30, schema may change] List all store locations (warehouses, retail counters). For inventory managers — use location_id to filter inventory queries per location.
AI agents call list_locations 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 retrieves store location data (warehouses, retail counters) without creating, modifying, deleting, or executing operations. It is purely informational and supports downstream queries. The undocumented status and potential schema changes do not elevate the risk category, only reduce confidence marginally.
From the tool's definition Tool name is 'list_locations' and description states 'List all store locations' — a retrieval operation with no modification or side effects. The stated use case is to 'filter inventory queries per location', which is read-only.
Documented attack patterns abuse exactly the kind of access list_locations 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_locations:
{
"version": "1",
"default": "deny",
"tools": {
"list_locations": {}
}
}list_locations 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] List all store locations (warehouses, retail counters). For inventory managers — use location_id to filter inventory queries per location. 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_locations: 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_locations 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_locations 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_locations. 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_locations 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.