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.
This record as markdown: /tools/ruflo/github-metrics.md
What github_metrics does on Ruflo
AI agents call github_metrics to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why github_metrics is rated Low
This tool queries and retrieves GitHub repository statistics. It performs no write, delete, execution, or financial operations. The user is merely fetching existing metrics data, making this a Read category risk with low severity.
From the tool's definition Tool name 'github_metrics' and description 'Get repository metrics and statistics' indicate retrieval of data with no side effects. The phrase 'Get repository metrics' is a read operation.
Attacks that exploit this kind of access
The rule that runs github_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every github_metrics call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. Nothing to install.
github_metrics 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_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.
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.
github_metrics is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue