create_automation

Create an automation. Checks the Automation app is installed first and installs it if needed. An automation = { name, type, status, rule }.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/create-automation.md

WHAT IT DOES

What create_automation does on Webcake Storefront

AI agents use create_automation 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.

RISK

Why create_automation is rated Medium

This tool creates new automation records in the storefront system. While it may trigger app installation as a prerequisite, the core function is creating structured data that can presumably be modified or deleted later. This is a reversible Write operation rather than Execute, because it does not directly run arbitrary code or external operations—it merely configures automation rules.

From the tool's definition Tool name 'create_automation' and description 'Create an automation' indicates data creation. The tool may automatically install the Automation app if needed, which is a side effect, but the primary action is creating a reversible data structure (an…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_automation 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 create_automation, this is the rule to start with:

create_automation Rate-limited

create_automation 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_automation": {
      "limits": [
        {
          "counter": "create_automation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every create_automation call is checked against it from then on.

FAQ

Questions about create_automation

What does the create_automation tool do? +

Create an automation. Checks the Automation app is installed first and installs it if needed. An automation = { name, type, status, rule }. 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.

How do I enforce a policy on create_automation? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for create_automation: 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.

What risk level is create_automation? +

create_automation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_automation? +

Yes. Add a rate_limit block to the create_automation 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.

How do I block create_automation completely? +

Set action: deny in the PolicyLayer policy for create_automation. 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.

What MCP server provides create_automation? +

create_automation 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.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →