This record as markdown: /tools/io-github-kivanccakmak-yaver/go-build.md
What go_build does on Yaver
AI agents invoke go_build to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
output | string | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why go_build is rated High
Building a Go project is an Execute action because build systems routinely invoke code: pre/post-build hooks, code generators, external commands, and dependencies can all execute arbitrary operations. The blast radius is high if a malicious agent uses this to compile and run untrusted code or trigger supply-chain compromises.
From the tool's definition Tool named 'go_build' with description 'Build Go project' — the term 'build' in a development context means compiling and executing build scripts, which can run arbitrary code during the build process (e.g., via go generate, build hooks, or embedded shell…
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs go_build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For go_build, this is the rule to start with:
go_build 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 Yaver, apply this rule, and every go_build call is checked against it from then on.
Questions about go_build
Build Go project. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
go_build accepts 2 parameters: output, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for go_build: 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 Yaver. Nothing to install.
go_build 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 go_build 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 go_build. 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.
go_build is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue