Create a new custom (manual) collection. For SEO/content team: set title, body_html,
AI agents use create_custom_collection to create or update resources in Sapo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sapo environment.
This tool creates new collection records in the Sapo.vn POS/e-commerce system, which is a reversible Write operation. It does not execute arbitrary code, delete data irreversibly, or transfer funds. The blast radius is medium because misconfigured collections could affect product visibility or SEO, but the operation can be undone by deleting the collection.
From the tool's definition Tool name 'create_custom_collection' and description 'Create a new custom (manual) collection' with parameters for title and body_html indicate creation of new data structures in the e-commerce platform.
Documented attack patterns abuse exactly the kind of access create_custom_collection 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 create_custom_collection:
{
"version": "1",
"default": "deny",
"tools": {
"create_custom_collection": {
"limits": [
{
"counter": "create_custom_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_custom_collection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new custom (manual) collection. For SEO/content team: set title, body_html,. It is categorised as a Write tool in the Sapo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sapo MCP server in PolicyLayer and add a rule for create_custom_collection: 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.
create_custom_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_custom_collection 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 create_custom_collection. 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.
create_custom_collection 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.