dispatch_workflow
Trigger an Actions workflow run (workflow_dispatch event)
This record as markdown: /tools/sqcows-forgejo-mcp/dispatch-workflow.md
What dispatch_workflow does on Forgejo
AI agents invoke dispatch_workflow to trigger actions in Forgejo. 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 dispatch_workflow is rated High
Executes arbitrary CI/CD workflow logic with effects determined by workflow definition and arguments.
From the tool's definition Trigger an Actions workflow run; workflow_dispatch event
Attacks that exploit this kind of access
The rule that runs dispatch_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dispatch_workflow, this is the rule to start with:
dispatch_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 Forgejo, apply this rule, and every dispatch_workflow call is checked against it from then on.
Questions about dispatch_workflow
Trigger an Actions workflow run (workflow_dispatch event). It is categorised as a Execute tool in the Forgejo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Forgejo MCP server in PolicyLayer and add a rule for dispatch_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 Forgejo. Nothing to install.
dispatch_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 dispatch_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 dispatch_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.
dispatch_workflow is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Forgejo, and thousands of servers like it.
Across the catalogue