golangci-lint

Runs golangci-lint and returns structured lint diagnostics (file, line, linter, severity, message).

SERVERBuild SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/golangci-lint.md

WHAT IT DOES

What golangci-lint does on Build

AI agents invoke golangci-lint to trigger actions in Build. 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.

RISK

Why golangci-lint is rated High

The tool executes an external linter process (golangci-lint) on the codebase. While it is read-only in intent (reporting diagnostics), it actively runs an external command whose effects depend on the arguments and environment, placing it in the Execute category. Misuse could expose source code details or be used to trigger resource-intensive analysis.

From the tool's definition Runs golangci-lint and returns structured lint diagnostics

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs golangci-lint safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For golangci-lint, this is the rule to start with:

golangci-lint Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "golangci-lint": {
      "limits": [
        {
          "counter": "golangci-lint_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about golangci-lint

What does the golangci-lint tool do? +

Runs golangci-lint and returns structured lint diagnostics (file, line, linter, severity, message). It is categorised as a Execute tool in the Build MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on golangci-lint? +

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

What risk level is golangci-lint? +

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

Can I rate-limit golangci-lint? +

Yes. Add a rate_limit block to the golangci-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.

How do I block golangci-lint completely? +

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

What MCP server provides golangci-lint? +

golangci-lint is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →