workflow_jobs_filter

Filters for workflow jobs. ONLY used when method is 'list_workflow_jobs' (object, optional)

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/workflow-jobs-filter.md

WHAT IT DOES

What workflow_jobs_filter does on GitHub

AI agents call workflow_jobs_filter to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why workflow_jobs_filter is rated Low

This tool retrieves and filters workflow job information for display/query purposes. It has no capability to execute workflows, modify jobs, delete data, or perform financial operations. The filtering operation is a read-only retrieval mechanism with no side effects.

From the tool's definition Tool name contains 'filter' and description states it is 'ONLY used when method is list_workflow_jobs', indicating it filters/queries existing workflow job data without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workflow_jobs_filter 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_jobs_filter, this is the rule to start with:

workflow_jobs_filter Allowed

workflow_jobs_filter is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workflow_jobs_filter": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about workflow_jobs_filter

What does the workflow_jobs_filter tool do? +

Filters for workflow jobs. ONLY used when method is 'list_workflow_jobs' (object, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on workflow_jobs_filter? +

Register the GitHub MCP server in PolicyLayer and add a rule for workflow_jobs_filter: 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_jobs_filter? +

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

Can I rate-limit workflow_jobs_filter? +

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

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

workflow_jobs_filter 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 →Data exfiltration →MCP token cost →