lint_code · Build MCP Server MCP: Risk & Policy

WHAT IT DOES

What lint_code does on Build MCP Server

AI agents invoke lint_code to trigger actions in Build MCP Server. 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.

WHY IT NEEDS A POLICY

Why lint_code needs a policy

This tool executes linting tools (eslint, prettier, flake8, etc.) which are external code analysis processes. While linting is typically read-only in intent, the execution happens through shell/command invocation and the actual linter behavior depends on configuration and arguments. The blast radius is high because misconfigured linters or linting scripts injected by an agent could execute arbitrary code.

From the tool's definition Tool description states 'Run linting on the codebase' which involves executing a linting process. The server description confirms it 'executing tests, analyzing package.json files, installing dependencies, and performing code linting' with support for…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lint_code Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lint_code": {
      "limits": [
        {
          "counter": "lint_code_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Build MCP Server, so you can run agents against it safely.

FAQ

Questions about lint_code

What does the lint_code tool do? +

Run linting on the codebase. It is categorised as a Execute tool in the Build MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lint_code? +

Register the Build MCP Server MCP server in PolicyLayer and add a rule for lint_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 Build MCP Server. Nothing to install.

What risk level is lint_code? +

lint_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lint_code? +

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

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

lint_code is provided by the Build MCP Server MCP server (teodortrotea/mcptest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.