gluecron_trigger_workflow
Dispatch a workflow_dispatch run. Mirrors POST /api/v2/repos/.../actions/workflows/:filename/dispatches. Requires 'repo' scope.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-trigger-workflow.md
What gluecron_trigger_workflow does on Gluecron
AI agents invoke gluecron_trigger_workflow to trigger actions in Gluecron. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
ref | string | — | Branch / tag / sha (default: repo default branch) |
repo | string | Yes | |
owner | string | Yes | |
inputs | object | — | Workflow inputs (object) |
filename | string | Yes | Workflow filename (e.g. ci.yml) |
Parameters from the server's own tool schema.
Why gluecron_trigger_workflow is rated High
This tool triggers CI/CD workflows, which execute code and arbitrary operations in the repository context. The effects are external and depend on what the workflow contains; this qualifies as Execute rather than Write since it invokes automated processes with side effects beyond simple data modification.
From the tool's definition "Dispatch a workflow_dispatch run" and "Mirrors POST /api/v2/repos/.../actions/workflows/:filename/dispatches" indicate triggering an external CI/CD workflow execution whose effects are determined by the workflow definition and arguments.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs gluecron_trigger_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_trigger_workflow, this is the rule to start with:
gluecron_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_trigger_workflow call is checked against it from then on.
Questions about gluecron_trigger_workflow
Dispatch a workflow_dispatch run. Mirrors POST /api/v2/repos/.../actions/workflows/:filename/dispatches. Requires 'repo' scope. It is categorised as a Execute tool in the Gluecron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gluecron_trigger_workflow accepts 5 parameters: ref, repo, owner, inputs, filename. Required: repo, owner, filename. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_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 Gluecron. Nothing to install.
gluecron_trigger_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gluecron_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.
Set action: deny in the PolicyLayer policy for gluecron_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.
gluecron_trigger_workflow is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
Across the catalogue