[UNDOCUMENTED endpoint, verified 2026-04-30, schema may change] List stock transfers between locations. For inventory managers — track goods movement between warehouses and retail counters. Returns paginated results via since_id cursor.
AI agents call list_stock_transfers 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 and queries stock transfer records between warehouse locations. It has no side effects, does not create, modify, or delete data, and does not execute external operations or move money. The primary function is informational — enabling inventory managers to view the history and status of goods movement.
From the tool's definition Tool description explicitly states 'List stock transfers' and 'track goods movement' — retrieval and querying of existing inventory transfer data with no modification capability. Returns paginated results via cursor, consistent with read-only list operations.
Documented attack patterns abuse exactly the kind of access list_stock_transfers 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_stock_transfers:
{
"version": "1",
"default": "deny",
"tools": {
"list_stock_transfers": {}
}
}list_stock_transfers 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 stock transfers between locations. For inventory managers — track goods movement between warehouses and retail counters. 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_stock_transfers: 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_stock_transfers 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_stock_transfers 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_stock_transfers. 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_stock_transfers 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.