This record as markdown: /tools/webcake-storefront/update-shipping.md
What update_shipping does on Webcake Storefront
AI agents use update_shipping 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 update_shipping is rated Medium
This tool modifies shipping configuration data, which is a reversible write operation. While not creating new data, it updates existing configuration that affects order fulfillment and customer operations. Severity is high because misconfiguration could disrupt business operations, orders, and customer experience, but it is not destructive (config can be reverted) or financial (does not directly move money).
From the tool's definition Tool name 'update_shipping' indicates modification of shipping configuration. Description states 'Update shipping config' which explicitly indicates a write/modification operation on storefront settings.
Attacks that exploit this kind of access
The rule that runs update_shipping 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 update_shipping, this is the rule to start with:
update_shipping 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 update_shipping call is checked against it from then on.
Questions about update_shipping
Update shipping config. Pass. 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 update_shipping: 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.
update_shipping 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 update_shipping 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 update_shipping. 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.
update_shipping 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