// MCP TOOL REFERENCE

LINT TOOLS

9 tools from the Lint MCP Server, categorised by risk level.

READ TOOLS

biome-check Runs Biome check (lint + format) and returns structured diagnostics (file, line, rule, severity, message). 2/5 format-check Checks if files are formatted and returns a structured list of files needing formatting. 2/5 hadolint Runs Hadolint (Dockerfile linter) and returns structured diagnostics (file, line, rule, severity, message). 2/5 lint Runs ESLint and returns structured diagnostics (file, line, column, rule, severity, message). 2/5 oxlint Runs Oxlint and returns structured diagnostics (file, line, column, rule, severity, message). 2/5 shellcheck Runs ShellCheck (shell script linter) and returns structured diagnostics (file, line, column, rule, severity, message). 2/5 stylelint Runs Stylelint and returns structured diagnostics (file, line, column, rule, severity, message). 2/5

WRITE TOOLS

biome-format Formats files with Biome (format --write) and returns a structured list of changed files. 3/5 prettier-format Formats files with Prettier (--write) and returns a structured list of changed files. 3/5

// FAQ

How many tools does the Lint MCP server have? +

The Lint MCP server exposes 9 tools across 2 categories: Read, Write.

How do I enforce policies on Lint tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Lint server.

What risk categories do Lint tools fall into? +

Lint tools are categorised as Read (7), Write (2). Each category has a recommended default policy.

Enforce policies on Lint

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →