count
Counts pattern matches per file using ripgrep. Returns per-file match counts and totals.
This record as markdown: /tools/io-github-dave-london-lint/count.md
What count does on Lint
AI agents call count to retrieve information from Lint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why count is rated Low
The tool performs read-only pattern searching and analysis using ripgrep, a standard code search utility. It returns counts and statistics but does not create, modify, delete, or execute any operations. This is a typical Read category tool used for code analysis and diagnostics.
From the tool's definition Tool 'counts pattern matches per file using ripgrep' and 'returns per-file match counts and totals' — this is a query/search operation that retrieves information without modifying, deleting, or executing code.
Attacks that exploit this kind of access
The rule that runs count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lint, 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 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 Lint, apply this rule, and every count call is checked against it from then on.
Questions about count
Counts pattern matches per file using ripgrep. Returns per-file match counts and totals. It is categorised as a Read tool in the Lint MCP Server, which means it retrieves data without modifying state.
Register the Lint 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 Lint. Nothing to install.
count 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 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.
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.
count is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lint, and thousands of servers like it.
This server
Across the catalogue