start_process

Start a new Process execution against a card. Resolves the process by ID or display name and creates an active Execution at the first workflow state (lowest rank). The Huly server

SERVERHuly SOURCEdugynoo/huly-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/start-process.md

WHAT IT DOES

What start_process does on Huly

AI agents invoke start_process to trigger actions in Huly. 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.

RISK

Why start_process is rated High

This tool executes a workflow process against a card, initiating a series of automated operations whose side effects are determined by the process definition and card state. While not immediately destructive, it represents a trigger for external automation that could have significant downstream consequences (notifications, state changes, further automations).

From the tool's definition Tool name 'start_process' and description states it 'Start a new Process execution' and 'creates an active Execution' — this triggers external workflow operations whose effects depend on which process is invoked and the card context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_process safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_process, this is the rule to start with:

start_process Rate-limited

start_process 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": {
    "start_process": {
      "limits": [
        {
          "counter": "start_process_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every start_process call is checked against it from then on.

FAQ

Questions about start_process

What does the start_process tool do? +

Start a new Process execution against a card. Resolves the process by ID or display name and creates an active Execution at the first workflow state (lowest rank). The Huly server. It is categorised as a Execute tool in the Huly MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_process? +

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

What risk level is start_process? +

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

Can I rate-limit start_process? +

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

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

start_process is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →