publish_workflow · Pulse Workflow MCP Server MCP

WHAT IT DOES

What publish_workflow does on Pulse Workflow MCP Server

AI agents use publish_workflow 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 publish_workflow needs a policy

Publishing a workflow version modifies the state of a workflow by promoting a draft to a published version. This is a Write operation because it creates/modifies data persistently but remains reversible through subsequent edits and version creation. It is not Execute (does not run arbitrary code), Destructive (previous versions remain accessible), or Financial.

From the tool's definition Tool name 'publish_workflow' and description 'Publish draft as new version' indicate creation or modification of workflow versions. The action commits a draft to a published state, which is reversible (a new version can be created/modified subsequently).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

publish_workflow Rate-limited

publish_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": {
    "publish_workflow": {
      "limits": [
        {
          "counter": "publish_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 Pulse Workflow MCP Server, so you can run agents against it safely.

FAQ

Questions about publish_workflow

What does the publish_workflow tool do? +

Publish draft as new version. 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 publish_workflow? +

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

What risk level is publish_workflow? +

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

Can I rate-limit publish_workflow? +

Yes. Add a rate_limit block to the publish_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 publish_workflow completely? +

Set action: deny in the PolicyLayer policy for publish_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 publish_workflow? +

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