List all repositories in the configured GitHub org.
AI agents call list_org_repositories to retrieve information from PR Reviewer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns repository metadata from a GitHub organization. It performs no mutations, deletions, or external operations. The retrieval of repository names and metadata is a read-only action with minimal blast radius — exposure would allow an attacker to enumerate repositories but not modify, delete, or execute anything.
From the tool's definition Tool name is 'list_org_repositories' and description states it 'List all repositories in the configured GitHub org' — a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
List all repositories in the configured GitHub org. It is categorised as a Read tool in the PR Reviewer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PR Reviewer MCP Server MCP server in PolicyLayer and add a rule for list_org_repositories: 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 PR Reviewer MCP Server. Nothing to install.
list_org_repositories 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_repositories 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_repositories. 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_repositories is provided by the PR Reviewer MCP Server MCP server (subhamyadav580/pr-reviewer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →