This record as markdown: /tools/io-github-dave-london-go/golangci-lint.md
What golangci-lint does on Go
AI agents invoke golangci-lint to trigger actions in Go. 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 golangci-lint is rated High
The tool executes an external linter process (golangci-lint) against code. While it primarily reads and reports, it actually runs an external command/tool, placing it in the Execute category. Misuse could involve running lint on arbitrary code paths, but blast radius is moderate since it is read-only in terms of data modification.
From the tool's definition Runs golangci-lint and returns structured lint diagnostics
Attacks that exploit this kind of access
The rule that runs golangci-lint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, 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 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 Go, apply this rule, and every golangci-lint call is checked against it from then on.
Questions about golangci-lint
Runs golangci-lint and returns structured lint diagnostics (file, line, linter, severity, message). It is categorised as a Execute tool in the Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Go 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 Go. Nothing to install.
golangci-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 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.
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.
golangci-lint is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue