github_metrics

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/github-metrics.md

WHAT IT DOES

What github_metrics does on Claude Flow

AI agents call github_metrics to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_metrics is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_metrics 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_metrics, this is the rule to start with:

github_metrics Allowed

github_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_metrics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every github_metrics call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →