update_custom_collection

THE RISK

Medium Risk

Why update_custom_collection needs a policy

This tool modifies existing collection metadata (title and HTML body content) but does not delete data or execute arbitrary code. The changes are reversible through additional update calls. The impact is limited to collection presentation and SEO metadata, affecting content visibility but not causing irreversible data loss or financial consequences.

From the tool's definition Tool description states "Update a custom collection" with modifications to "title, body_html". These are reversible modifications to existing content.

Documented attack patterns abuse exactly the kind of access update_custom_collection gives an agent:

POLICY

How to control update_custom_collection

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 update_custom_collection:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_custom_collection": {
      "limits": [
        {
          "counter": "update_custom_collection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_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.

Create a free account and register Sapo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sapo tools

Financial create_order_transaction Create a transaction for an order (e.g. capture, sale, refund). Side effect: creates a Tra Execute create_script_tag Inject a new JavaScript file into the storefront. For SEO/content team: Execute send_draft_order_invoice Send an invoice email for a draft order. Side effect: sends email to customer; draft statu Write adjust_inventory_level Adjust inventory level by a relative delta (positive = receive stock, negative = remove st Write add_customer_address Add a new address to a customer. Required: address1, city, country. Write complete_draft_order Complete a draft order and convert it into a real order. Side effect: creates an Order fro Write connect_inventory_level Connect an inventory item to a location (enable tracking at that location). For store owne Write create_article Create a new article within a blog. For SEO/content team: provide title, HTML body,

All 93 Sapo tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_custom_collection

What does the update_custom_collection tool do? +

Update a custom collection. For SEO/content team: update 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.

How do I enforce a policy on update_custom_collection? +

Register the Sapo MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_custom_collection? +

update_custom_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_custom_collection? +

Yes. Add a rate_limit block to the update_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.

How do I block update_custom_collection completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_custom_collection? +

update_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.

Enforce policy on every Sapo tool call.

Start from Sapo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →