edit_http_function
Edit the HTTP function file by function name — best for targeted changes (fix a bug, rename, add one function). For writing multiple new functions or major refactors, use update_http_function with full content instead. Actions: -
This record as markdown: /tools/webcake-storefront/edit-http-function.md
What edit_http_function does on Webcake Storefront
AI agents use edit_http_function 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 edit_http_function is rated Medium
This tool modifies existing HTTP function files on the storefront server. While it is reversible in principle (the file can be re-edited), it changes executable server-side code, which carries a high blast radius — a malicious or incorrect edit could break storefront functionality, introduce security vulnerabilities, or expose customer data.
From the tool's definition 'Edit the HTTP function file by function name — best for targeted changes (fix a bug, rename, add one function)'
Attacks that exploit this kind of access
The rule that runs edit_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 edit_http_function, this is the rule to start with:
edit_http_function 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 edit_http_function call is checked against it from then on.
Questions about edit_http_function
Edit the HTTP function file by function name — best for targeted changes (fix a bug, rename, add one function). For writing multiple new functions or major refactors, use update_http_function with full content instead. Actions: -. 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 edit_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.
edit_http_function 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 edit_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 edit_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.
edit_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.
This server
Across the catalogue