filter

Filter notifications to, use default unless specified. Read notifications are ones that have already been acknowledged by the user. Participating notifications are those that the user is directly involved in, such as issues or pull requests they have commented on or created. (string, 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/filter.md

WHAT IT DOES

What filter does on GitHub

AI agents call 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 filter is rated Low

This is a filtering/querying tool that helps users retrieve and categorize existing notifications. It does not create, modify, delete, or execute any operations - it only retrieves notification metadata already present in GitHub. The blast radius of misuse is minimal as it only affects what notifications are displayed to the user, with no persistent changes to data or systems.

From the tool's definition Tool filters notifications with read status and participating status - it retrieves and queries notification data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

filter Allowed

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": {
    "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 filter call is checked against it from then on.

FAQ

Questions about filter

What does the filter tool do? +

How do I enforce a policy on filter? +

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

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

Can I rate-limit filter? +

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

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

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 →