projects_list
List GitHub Projects resources
This record as markdown: /tools/io-github-aifity-omnigit-mcp/projects-list.md
What projects_list does on GitHub
AI agents call projects_list 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 projects_list is rated Low
This tool retrieves or queries project information from GitHub without modifying, executing, or deleting any data. It is a straightforward list/retrieval operation that falls squarely into the Read category. The blast radius is minimal since listing public or authorized project metadata cannot cause harm unless the data itself is sensitive, but the operation itself is non-destructive and non-privileged in nature.
From the tool's definition Tool name is 'projects_list' and description states 'List GitHub Projects resources'. The verb 'list' combined with 'resources' indicates a read-only data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs projects_list 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 projects_list, this is the rule to start with:
projects_list 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 projects_list call is checked against it from then on.
Questions about projects_list
List GitHub Projects resources. 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 projects_list: 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.
projects_list 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 projects_list 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 projects_list. 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.
projects_list 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