workflow_id

The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for 'run_workflow' method. (string, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Other

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-aifity-omnigit-mcp/workflow-id.md

WHAT IT DOES

What workflow_id does on GitHub

AI agents call workflow_id as a supporting operation in GitHub workflows.

RISK

Why workflow_id is rated Low

This appears to be a parameter descriptor rather than an executable tool. It describes an input field (workflow ID or filename) used by another tool ('run_workflow'). It has no independent action or side effect. Confidence is low because the description is uninformative as a standalone tool.

From the tool's definition The description says 'The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for run_workflow method.' This is a parameter/identifier field, not an actionable tool itself.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workflow_id safely

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

workflow_id Rate-limited

workflow_id gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workflow_id": {
      "limits": [
        {
          "counter": "workflow_id_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about workflow_id

What does the workflow_id tool do? +

The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for 'run_workflow' method. (string, optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on workflow_id? +

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

What risk level is workflow_id? +

workflow_id is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit workflow_id? +

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

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

workflow_id is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →