count

Counts pattern matches per file using ripgrep. Returns per-file match counts and totals.

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/count.md

WHAT IT DOES

What count does on Git

AI agents call count 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 count is rated Low

This tool retrieves and reports pattern match statistics across files. It is a read-only operation that queries file contents without side effects, modifying state, or executing arbitrary code. The blast radius of misuse is minimal—an agent could only gather information about file contents matching patterns.

From the tool's definition Tool 'count' uses ripgrep to count pattern matches per file and returns match counts and totals. The description indicates it performs search/query operations with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

count Allowed

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

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 count call is checked against it from then on.

FAQ

Questions about count

What does the count tool do? +

Counts pattern matches per file using ripgrep. Returns per-file match counts and totals. 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 count? +

Register the Git MCP server in PolicyLayer and add a rule for count: 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 count? +

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

Can I rate-limit count? +

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

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

count 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 →