stats

Returns a snapshot of container resource usage (CPU, memory, network/block I/O, PIDs) as structured data.

SERVERGit SOURCEDave-London/Pare

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-dave-london-git/stats.md

WHAT IT DOES

What stats does on Git

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

RISK

Why stats is rated Low

This tool queries and retrieves current container metrics without side effects. It is purely informational and diagnostic in nature, fitting the 'Read' category for data retrieval operations. The low severity reflects that exposing resource usage statistics poses minimal risk even if an AI agent calls it arbitrarily.

From the tool's definition Tool 'stats' returns a snapshot of container resource usage metrics (CPU, memory, network/block I/O, PIDs) as structured data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stats, this is the rule to start with:

stats Allowed

stats 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": {
    "stats": {}
  }
}

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

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

FAQ

Questions about stats

What does the stats tool do? +

Returns a snapshot of container resource usage (CPU, memory, network/block I/O, PIDs) as structured data. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stats? +

Register the Git MCP server in PolicyLayer and add a rule for stats: 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 Git. Nothing to install.

What risk level is stats? +

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

Can I rate-limit stats? +

Yes. Add a rate_limit block to the stats 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 stats completely? +

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

stats is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

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