lint
Run linter on the project. Auto-detects: go vet, eslint, ruff/flake8, clippy.
This record as markdown: /tools/io-github-kivanccakmak-yaver/lint.md
What lint does on Yaver
AI agents invoke lint to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
tool | string | — | Custom lint command (auto-detected if empty) |
directory | string | — | Project directory |
Parameters from the server's own tool schema.
Why lint is rated High
The lint tool executes external linting processes on the user's codebase. While linters are generally safe development tools with read-only intentions, they execute arbitrary code/processes whose behavior depends on project configuration and linting rules. This falls under Execute rather than Read because it invokes external tools/processes.
From the tool's definition Tool description states 'Run linter on the project' with auto-detection of language-specific linting tools (go vet, eslint, ruff/flake8, clippy). The verb 'Run' combined with execution of external linting processes constitutes code execution.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs lint 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 lint, this is the rule to start with:
lint stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 lint call is checked against it from then on.
Questions about lint
Run linter on the project. Auto-detects: go vet, eslint, ruff/flake8, clippy. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
lint 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 lint: 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.
lint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lint 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 lint. 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.
lint 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.
Across the catalogue