Manage GitHub repositories: list, view, create, clone, fork.
AI agents use gh_repos to create or update resources in RedisNexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RedisNexus environment.
While 'list' and 'view' are Read operations, the tool also enables 'create, clone, fork' which create new repositories or repository copies. These are Write operations that create persistent artifacts. Although fork/clone are technically reversible (repos can be deleted), they modify the landscape of repositories and represent resource creation.
From the tool's definition Tool performs actions that create or modify data: 'create, clone, fork' are irreversible or create new resources. The description explicitly lists create, clone, and fork operations which go beyond read-only retrieval.
Attacks that exploit this kind of access
Manage GitHub repositories: list, view, create, clone, fork. It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RedisNexus MCP server in PolicyLayer and add a rule for gh_repos: 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 RedisNexus. Nothing to install.
gh_repos is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gh_repos 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 gh_repos. 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.
gh_repos is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). 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 →