// MCP TOOL REFERENCE

GO TOOLS

11 tools from the Go MCP Server, categorised by risk level.

READ TOOLS

env Returns Go environment variables as structured JSON. Optionally request specific variables. fmt Checks or fixes Go source formatting using gofmt. In check mode (-l), lists unformatted files. In fix mode (-w), rewrites files. 2/5 get Downloads and installs Go packages and their dependencies. 2/5 golangci-lint Runs golangci-lint and returns structured lint diagnostics (file, line, linter, severity, message). 2/5 list Lists Go packages or modules and returns structured information. When `modules` is true, lists modules (with path, version, dir); otherwise lists p... 2/5 test Runs go test and returns structured test results (name, status, package, elapsed). 2/5 vet Runs go vet and returns structured static analysis diagnostics with analyzer names. Uses -json flag for native JSON output with automatic text fall...

WRITE TOOLS

generate Runs go generate directives in Go source files. WARNING: may execute untrusted code. 3/5

DESTRUCTIVE TOOLS

mod-tidy Runs go mod tidy to add missing and remove unused module dependencies. 5/5

EXECUTE TOOLS

build Runs go build and returns structured error list (file, line, column, message). 4/5 run Runs a Go program and returns structured output (stdout, stderr, exit code). 5/5

// FAQ

How many tools does the Go MCP server have? +

The Go MCP server exposes 11 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Go 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 Go server.

What risk categories do Go tools fall into? +

Go tools are categorised as Read (7), Write (1), Destructive (1), Execute (2). Each category has a recommended default policy.

Enforce policies on Go

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →