List custom (manual) collections. For SEO/content team: use to browse collections
AI agents call list_custom_collections 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 displays existing collection data without creating, modifying, deleting, or executing any changes. It is purely informational, with no side effects or destructive potential. The low blast radius reflects that listing collections cannot harm the system or data.
From the tool's definition Tool name 'list_custom_collections' and description 'List custom (manual) collections' indicate a retrieval operation with no modification capability. Intended use is to 'browse collections', a read-only action.
Documented attack patterns abuse exactly the kind of access list_custom_collections 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_custom_collections:
{
"version": "1",
"default": "deny",
"tools": {
"list_custom_collections": {}
}
} list_custom_collections 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 custom (manual) collections. For SEO/content team: use to browse collections. 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_custom_collections: 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_custom_collections 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_custom_collections 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_custom_collections. 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_custom_collections 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.