upsert_customer_tag

Create or update a customer tag. Omit

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/upsert-customer-tag.md

WHAT IT DOES

What upsert_customer_tag does on Webcake Storefront

AI agents use upsert_customer_tag to create or update resources in Webcake Storefront, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webcake Storefront environment.

RISK

Why upsert_customer_tag is rated Medium

The tool performs upsert (create or update) operations on customer tags, which are data modifications. These changes are reversible (tags can be deleted or modified again), so this is a Write operation rather than Destructive.

From the tool's definition Tool name 'upsert_customer_tag' and description 'Create or update a customer tag' indicate reversible creation or modification of customer metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs upsert_customer_tag safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upsert_customer_tag, this is the rule to start with:

upsert_customer_tag Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every upsert_customer_tag call is checked against it from then on.

FAQ

Questions about upsert_customer_tag

What does the upsert_customer_tag tool do? +

Create or update a customer tag. Omit. It is categorised as a Write tool in the Webcake Storefront MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upsert_customer_tag? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for upsert_customer_tag: 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 Webcake Storefront. Nothing to install.

What risk level is upsert_customer_tag? +

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

Can I rate-limit upsert_customer_tag? +

Yes. Add a rate_limit block to the upsert_customer_tag 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 upsert_customer_tag completely? +

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

upsert_customer_tag is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_tag on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →