trigger_workflow

Trigger GitHub Actions workflow

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/trigger-workflow.md

WHAT IT DOES

What trigger_workflow does on Ncp

AI agents invoke trigger_workflow to trigger actions in Ncp. 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 trigger_workflow is rated High

Triggering GitHub Actions workflows executes code in a production environment, potentially deploying applications, modifying repositories, running tests against live systems, or executing arbitrary scripts. This is a classic Execute action with high blast radius if triggered maliciously or with incorrect arguments.

From the tool's definition Tool description states 'Trigger GitHub Actions workflow' — this directly executes external operations (GitHub Actions CI/CD pipelines) whose effects depend on the workflow configuration and arguments provided.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trigger_workflow safely

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

trigger_workflow Rate-limited

trigger_workflow 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": {
    "trigger_workflow": {
      "limits": [
        {
          "counter": "trigger_workflow_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 Ncp, apply this rule, and every trigger_workflow call is checked against it from then on.

FAQ

Questions about trigger_workflow

What does the trigger_workflow tool do? +

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

How do I enforce a policy on trigger_workflow? +

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

What risk level is trigger_workflow? +

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

Can I rate-limit trigger_workflow? +

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

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

trigger_workflow is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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