workflow_runs_filter
Filters for workflow runs. ONLY used when method is 'list_workflow_runs' (object, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/workflow-runs-filter.md
What workflow_runs_filter does on GitHub
AI agents call workflow_runs_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.
Why workflow_runs_filter is rated Low
This tool filters and queries existing workflow run data without modifying, executing, or deleting anything. It is a read operation that retrieves or queries data, matching the 'Read' category. The low severity reflects that filtering workflow runs poses minimal risk even if misused by an agent.
From the tool's definition Tool description states it 'Filters for workflow runs' and is 'ONLY used when method is list_workflow_runs'. The 'list' operation is a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs workflow_runs_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_runs_filter, this is the rule to start with:
workflow_runs_filter is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every workflow_runs_filter call is checked against it from then on.
Questions about workflow_runs_filter
Filters for workflow runs. ONLY used when method is 'list_workflow_runs' (object, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for workflow_runs_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.
workflow_runs_filter is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the workflow_runs_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.
Set action: deny in the PolicyLayer policy for workflow_runs_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.
workflow_runs_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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue