AI agents use create_workflow to create or update resources in Automatisch MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automatisch MCP Server environment.
Creating a workflow is a reversible write operation—new workflows can be modified or deleted later. It does not execute arbitrary code, delete data irreversibly, or move money. The medium severity reflects that a misconfigured workflow could trigger unwanted automation actions depending on its contents, but the operation itself is reversible.
From the tool's definition Tool name and description indicate creation of a new workflow: "Create a new workflow". This is a write operation that creates reversible data structures in the workflow automation platform.
Documented attack patterns abuse exactly the kind of access create_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automatisch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"create_workflow": {
"limits": [
{
"counter": "create_workflow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_workflow 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.
Free to start. No card required.
Create a new workflow. It is categorised as a Write tool in the Automatisch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automatisch MCP Server MCP server in PolicyLayer and add a rule for create_workflow: 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 Automatisch MCP Server. Nothing to install.
create_workflow 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 create_workflow 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 create_workflow. 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.
create_workflow is provided by the Automatisch MCP Server MCP server (milisp/automatisch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automatisch MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Automatisch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.