update_http_function
Write the FULL HTTP function file content. Best for: writing new features, major refactors, or changes that touch multiple functions. For small targeted edits (fix one function, add one function), use edit_http_function instead. After update, auto-deploys to the bundle service
This record as markdown: /tools/webcake-storefront/update-http-function.md
What update_http_function does on Webcake Storefront
AI agents invoke update_http_function to trigger actions in Webcake Storefront. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why update_http_function is rated High
This tool writes complete HTTP function files and immediately auto-deploys them to a live bundle service. The auto-deploy aspect makes this Execute rather than Write, as it triggers external operations (deployment) with potentially wide blast radius. An AI agent misusing this could deploy malicious or broken code to production, affecting all storefront visitors.
From the tool's definition 'Write the FULL HTTP function file content' and 'auto-deploys to the bundle service' — overwrites entire function files and triggers automatic deployment to production infrastructure
Attacks that exploit this kind of access
The rule that runs update_http_function 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_http_function, this is the rule to start with:
update_http_function stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_http_function call is checked against it from then on.
Questions about update_http_function
Write the FULL HTTP function file content. Best for: writing new features, major refactors, or changes that touch multiple functions. For small targeted edits (fix one function, add one function), use edit_http_function instead. After update, auto-deploys to the bundle service. It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for update_http_function: 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_http_function is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the update_http_function 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_http_function. 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_http_function 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.
Across the catalogue