trigger-workflow · GitHub Enterprise MCP Server MCP

WHAT IT DOES

What trigger-workflow does on GitHub Enterprise MCP Server

AI agents invoke trigger-workflow to trigger actions in GitHub Enterprise 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 trigger-workflow needs a policy

This tool executes external operations (GitHub Actions workflows) whose effects are determined by the workflow definition and arguments passed. Workflows can perform arbitrary tasks—building, testing, deploying, or running scripts—making this an Execute category risk.

From the tool's definition Tool name 'trigger-workflow' and description 'Trigger a workflow run in a GitHub repository' indicate execution of automated workflows whose behavior and side effects depend on the specific workflow being triggered.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

FAQ

Questions about trigger-workflow

What does the trigger-workflow tool do? +

Trigger a workflow run in a GitHub repository. It is categorised as a Execute tool in the GitHub Enterprise 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 trigger-workflow? +

Register the GitHub Enterprise MCP Server 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 GitHub Enterprise MCP Server. 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 GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.