This record as markdown: /tools/io-github-kivanccakmak-yaver/loc-count.md
What loc_count does on Yaver
AI agents call loc_count to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tool | string | — | Preferred tool: tokei, scc, cloc |
directory | string | — |
Parameters from the server's own tool schema.
Why loc_count is rated Low
This tool queries and reports a metric (line count) from source code without creating, modifying, deleting, or executing any code. It is a read-only operation that gathers information for analysis purposes.
From the tool's definition Tool description explicitly states 'Count lines of code' using analysis tools (tokei/scc/cloc). No modification, deletion, execution of external operations, or financial transactions occur. The action is purely analytical retrieval of code metrics.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs loc_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For loc_count, this is the rule to start with:
loc_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 Yaver, apply this rule, and every loc_count call is checked against it from then on.
Questions about loc_count
Count lines of code (uses tokei/scc/cloc with fallbacks). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
loc_count accepts 2 parameters: tool, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for loc_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 Yaver. Nothing to install.
loc_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 loc_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 loc_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.
loc_count is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue