list_org_repository_security_advisories
List repository security advisories for a GitHub organization.
This record as markdown: /tools/github/list-org-repository-security-advisories.md
What list_org_repository_security_advisories does on GitHub
AI agents call list_org_repository_security_advisories 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
org | string | — | The organization login. |
sort | string | — | Sort field. |
state | string | — | Filter by advisory state. |
direction | string | — | Sort direction. |
Parameters from the server's own tool schema.
Why list_org_repository_security_advisories is rated Low
This tool retrieves security advisory information from GitHub repositories without modifying, deleting, or executing any actions. It is fundamentally a read operation. Severity is medium rather than low because security advisories contain sensitive vulnerability information that could be misused if an AI agent inappropriately disclosed or aggregated this data across multiple organizations, but the tool itself…
From the tool's definition Tool name and description indicate it 'List repository security advisories' - a retrieval operation with no modification or deletion capability. The function retrieves and queries security advisory data.
Attacks that exploit this kind of access
The rule that runs list_org_repository_security_advisories 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 list_org_repository_security_advisories, this is the rule to start with:
list_org_repository_security_advisories 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 list_org_repository_security_advisories call is checked against it from then on.
Questions about list_org_repository_security_advisories
List repository security advisories for a GitHub organization. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
list_org_repository_security_advisories accepts 4 parameters: org, sort, state, direction. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for list_org_repository_security_advisories: 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.
list_org_repository_security_advisories 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 list_org_repository_security_advisories 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 list_org_repository_security_advisories. 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.
list_org_repository_security_advisories is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.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