create_app · Pulse Workflow MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_app does on Pulse Workflow MCP Server

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

WHY IT NEEDS A POLICY

Why create_app needs a policy

This tool creates and initializes a new app/workflow, which is a reversible write operation. It has moderate blast radius—an AI agent could create numerous unnecessary apps or initialize workflows with incorrect configurations—but the action is not destructive (can be undone) or irreversible. It does not execute arbitrary code, move money, or permanently delete data.

From the tool's definition Tool name 'create_app' and description 'Create app and auto-initialize workflow' indicate a tool that creates (writes) new resources. The return of id, name, mode, start_node_id confirms persistent data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_app Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_app": {
      "limits": [
        {
          "counter": "create_app_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 Pulse Workflow MCP Server, so you can run agents against it safely.

FAQ

Questions about create_app

What does the create_app tool do? +

Create app and auto-initialize workflow. Returns: {id, name, mode, start_node_id}. It is categorised as a Write tool in the Pulse Workflow 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_app? +

Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for create_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 Pulse Workflow MCP Server. Nothing to install.

What risk level is create_app? +

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

Can I rate-limit create_app? +

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

How do I block create_app completely? +

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

What MCP server provides create_app? +

create_app is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.