Analyze a GitHub repository 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.
AI agents call github_repo_analyze to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes repository data without modifying it. Analysis is a Read operation with minimal blast radius if misused by an AI agent—it gathers information about code state and metrics. The emphasis on using it for Ruflo-specific state inspection (rather than commands) confirms it is introspective. Low severity because no irreversible changes or external execution can result from analysis alone.
From the tool's definition Tool name 'analyze' and description 'Analyze a GitHub repository' indicate read-only introspection. The guidance to use it only when 'native Bash / file tools are wrong' and preference for one-line commands further suggests querying or examining state, not…
Attacks that exploit this kind of access
Analyze a GitHub repository 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 Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for github_repo_analyze: 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_repo_analyze 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 github_repo_analyze 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_repo_analyze. 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_repo_analyze 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.