install_app
Install (register) an application on the current site so its features become usable. For example, automations need the
This record as markdown: /tools/webcake-storefront/install-app.md
What install_app does on Webcake Storefront
AI agents use install_app 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 install_app is rated Medium
Installing an app modifies the site configuration by adding a new application and enabling its features. This is a reversible Write operation (the app can typically be uninstalled), not a Read (no data retrieval), Execute (no arbitrary code execution), Destructive (reversible), or Financial operation.
From the tool's definition Tool name "install_app" and description "Install (register) an application on the current site so its features become usable" indicates creating/registering a new application resource on the storefront.
Attacks that exploit this kind of access
The rule that runs install_app 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 install_app, this is the rule to start with:
install_app 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 install_app call is checked against it from then on.
Questions about install_app
Install (register) an application on the current site so its features become usable. For example, automations need the. 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 install_app: 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.
install_app 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 install_app 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 install_app. 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.
install_app 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