startWorkflow · AEM MCP Server MCP: Risk & Policy

WHAT IT DOES

What startWorkflow does on AEM MCP Server

AI agents invoke startWorkflow to trigger actions in AEM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why startWorkflow needs a policy

This tool triggers execution of pre-defined workflow processes in AEM. While workflows themselves are system-defined, the act of starting a workflow initiates side effects that may include content changes, notifications, third-party integrations, or approval chains. An AI agent with improper workflow selection or parameters could trigger unintended business processes, data modifications, or external system calls.

From the tool's definition Tool name: 'startWorkflow'; description: 'Start an AEM workflow'. The verb 'start' combined with 'workflow' indicates triggering an external operation whose effects depend on workflow configuration and arguments passed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

startWorkflow Rate-limited

startWorkflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "startWorkflow": {
      "limits": [
        {
          "counter": "startworkflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about startWorkflow

What does the startWorkflow tool do? +

Start an AEM workflow. It is categorised as a Execute tool in the AEM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on startWorkflow? +

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

What risk level is startWorkflow? +

startWorkflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit startWorkflow? +

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

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

startWorkflow is provided by the AEM MCP Server MCP server (udaykumarbpatel/aem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.