common-invoke-workflow-by-path

Executes workflow action for a Sitecore item by its path.

Accepts file system path (path)

Part of the Mcp Sitecore MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@antonytm/mcp-sitecore-server Execute Risk 4/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke common-invoke-workflow-by-path to trigger processes or run actions in Mcp Sitecore. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON COMMON-INVOKE-WORKFLOW-BY-PATH

common-invoke-workflow-by-path can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-antonytm-mcp-sitecore-server.yaml

tools:
  common-invoke-workflow-by-path:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mcp Sitecore policy for all 153 tools.

// DETAILS

Tool Name common-invoke-workflow-by-path

Category Execute

MCP Server Mcp Sitecore MCP Server

Risk Level High

// MORE MCP SITECORE TOOLS

Destructive common-remove-archive-item Destructive common-remove-base-template-by-id Destructive common-remove-base-template-by-path Destructive common-remove-item-version-by-id Destructive common-remove-item-version-by-path Destructive common-reset-item-field-by-id Destructive common-reset-item-field-by-path Destructive indexing-remove-search-index-item-by-id

View all 153 tools →

// RELATED READING

// FAQ

What does the common-invoke-workflow-by-path tool do? +

Executes workflow action for a Sitecore item by its path.. It is categorised as a Execute tool in the Mcp Sitecore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on common-invoke-workflow-by-path? +

Add a rule in your Intercept YAML policy under the tools section for common-invoke-workflow-by-path. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Sitecore MCP server.

What risk level is common-invoke-workflow-by-path? +

common-invoke-workflow-by-path is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit common-invoke-workflow-by-path? +

Yes. Add a rate_limit block to the common-invoke-workflow-by-path rule in your Intercept 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 common-invoke-workflow-by-path completely? +

Set action: deny in the Intercept policy for common-invoke-workflow-by-path. 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 common-invoke-workflow-by-path? +

common-invoke-workflow-by-path is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

common-invoke-workflow-by-path

Enforce policies on Mcp Sitecore