cwes
Filter by Common Weakness Enumeration IDs (e.g. ["79", "284", "22"]). (string[], optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/cwes.md
What cwes does on GitHub
AI agents call cwes 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 cwes is rated Low
This is a filter parameter for querying security vulnerability data (CWEs). It retrieves or filters existing information without creating, modifying, deleting, or executing any operations. It presents minimal risk as a standalone read operation.
From the tool's definition Tool name 'cwes' and description indicate filtering by Common Weakness Enumeration IDs—a query/filter operation with no side effects. The parameter is a string array of CWE identifiers used to narrow results, consistent with read-only data retrieval.
Attacks that exploit this kind of access
The rule that runs cwes 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 cwes, this is the rule to start with:
cwes 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 cwes call is checked against it from then on.
Questions about cwes
Filter by Common Weakness Enumeration IDs (e.g. ["79", "284", "22"]). (string[], 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 cwes: 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.
cwes 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 cwes 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 cwes. 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.
cwes 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