github_metrics

Get repository metrics and statistics 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.

Server Claude Flow claude-flow
Category Read
Risk class Low
Parameters 00 required

What github_metrics does on Claude Flow

AI agents call github_metrics 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.

Why github_metrics needs a policy

This tool retrieves repository metrics and statistics from GitHub, which is a query operation that does not modify, delete, or execute any operations. It has no side effects beyond fetching read-only data. The mention of 'Ruflo-specific state or controllers' does not change the fundamental read-only nature.

From the tool's definition Tool name 'github_metrics' and description 'Get repository metrics and statistics' indicate data retrieval only. The phrase 'Get' and 'metrics and statistics' are characteristic of read operations with no side effects.

Questions about github_metrics

What does the github_metrics tool do? +

Get repository metrics and statistics 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.

How do I enforce a policy on github_metrics? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for github_metrics: 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.

What risk level is github_metrics? +

github_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit github_metrics? +

Yes. Add a rate_limit block to the github_metrics 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.

How do I block github_metrics completely? +

Set action: deny in the PolicyLayer policy for github_metrics. 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.

What MCP server provides github_metrics? +

github_metrics 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.