assign_customer_tags
Add or remove tags on multiple customers at once.
This record as markdown: /tools/webcake-storefront/assign-customer-tags.md
What assign_customer_tags does on Webcake Storefront
AI agents use assign_customer_tags 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.
Why assign_customer_tags is rated Medium
This tool modifies customer data (tags) but the changes are reversible: tags can be added and removed. It affects potentially many customers ('multiple customers at once') which increases blast radius, but there is no permanent deletion or data destruction. The impact is primarily on customer attributes rather than transactional or financial systems, making it Write rather than Execute or higher severity categories.
From the tool's definition Tool performs 'Add or remove tags on multiple customers' — these are reversible modifications to customer metadata. The description explicitly states both add and remove operations on customer records.
Attacks that exploit this kind of access
The rule that runs assign_customer_tags 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 assign_customer_tags, this is the rule to start with:
assign_customer_tags 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every assign_customer_tags call is checked against it from then on.
Questions about assign_customer_tags
Add or remove tags on multiple customers at once. 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.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for assign_customer_tags: 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.
assign_customer_tags 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 assign_customer_tags 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 assign_customer_tags. 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.
assign_customer_tags 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.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue