create_workflow · Prowpt MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_workflow does on Prowpt MCP Server

AI agents use create_workflow to create or update resources in Prowpt MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prowpt MCP Server environment.

WHY IT NEEDS A POLICY

Why create_workflow needs a policy

This tool creates a new workflow resource on the platform. While workflows can trigger external operations (webhooks, stripe events, cron jobs), the act of creating a workflow is a Write operation — it persistently stores a configuration. Misuse could wire up unintended automation, raising severity to medium. The most severe aspect is creation/modification rather than immediate destructive or financial action.

From the tool's definition 'Create a workflow' with trigger types including form_submit, button_click, cron, chat_message, webhook, stripe_event — creates a new workflow configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_workflow Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Prowpt MCP Server, so you can run agents against it safely.

FAQ

Questions about create_workflow

What does the create_workflow tool do? +

Create a workflow. Trigger types: form_submit, button_click, cron, chat_message, webhook (inbound HTTP), stripe_event. IMPORTANT node structure: each node needs type=. It is categorised as a Write tool in the Prowpt MCP Server 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_workflow? +

Register the Prowpt 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 Prowpt MCP Server. Nothing to install.

What risk level is create_workflow? +

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

Can I rate-limit create_workflow? +

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.

How do I block create_workflow completely? +

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.

What MCP server provides create_workflow? +

create_workflow is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.