path_filter

What path_filter does on GitHub

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

This is a Read operation. It filters query results to display a subset of files in a repository directory structure. The term 'filter' and the example use case ('show files in the src directory') confirm this is a non-destructive data retrieval aid. There is no capability to modify, execute, or delete data. Severity is low because misuse would only expose information already accessible in the repository.

From the tool's definition Tool is described as a filter parameter for 'tree results' that 'only show files in the src directory'. It retrieves or queries data with no side effects—it filters existing filesystem/repository data without modifying, creating, or deleting anything.

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

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

Questions about path_filter