github_pr_manage
Manage pull requests Use when native Bash / file tools are wrong because this MCP tool exposes Ruflo-specific state or controllers that have no shell equivalent. For tasks that fit a one-line native command, prefer that.
This record as markdown: /tools/io-github-ruvnet-claude-flow/github-pr-manage.md
What github_pr_manage does on Claude Flow
AI agents use github_pr_manage to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why github_pr_manage is rated Medium
Pull request management typically involves creating, updating, closing, or merging PRs—all reversible write operations. While the description lacks detail on specific actions (create vs. merge vs. close), the word 'manage' combined with 'state...controllers' implies modification capability rather than pure retrieval.
From the tool's definition Tool name 'github_pr_manage' and description 'Manage pull requests' indicates creation, modification, or state changes to PR objects. The phrase 'exposes Ruflo-specific state or controllers' suggests manipulation of PR resources rather than read-only access.
Attacks that exploit this kind of access
The rule that runs github_pr_manage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_pr_manage, this is the rule to start with:
github_pr_manage stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every github_pr_manage call is checked against it from then on.
Questions about github_pr_manage
Manage pull requests Use when native Bash / file tools are wrong because this MCP tool exposes Ruflo-specific state or controllers that have no shell equivalent. For tasks that fit a one-line native command, prefer that. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for github_pr_manage: 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 Claude Flow. Nothing to install.
github_pr_manage 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 github_pr_manage 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 github_pr_manage. 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.
github_pr_manage is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue