lines_of_code

Count lines of code by language.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/lines-of-code.md

WHAT IT DOES

What lines_of_code does on Yaver

AI agents call lines_of_code 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
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why lines_of_code is rated Low

This tool performs a read-only analysis of code metrics. It queries existing source code to count lines by programming language. There are no side effects, no code execution, no data modification, and no destructive operations. The operation is informational and safe for an AI agent to invoke.

From the tool's definition Tool name 'lines_of_code' and description 'Count lines of code by language' indicate a query/analysis operation that retrieves metrics about source code without modifying, executing, or deleting anything.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

lines_of_code Allowed

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

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

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

FAQ

Questions about lines_of_code

What does the lines_of_code tool do? +

Count lines of code by language. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does lines_of_code accept? +

lines_of_code accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on lines_of_code? +

Register the Yaver MCP server in PolicyLayer and add a rule for lines_of_code: 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.

What risk level is lines_of_code? +

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

Can I rate-limit lines_of_code? +

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

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

lines_of_code 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

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