This record as markdown: /tools/io-github-kivanccakmak-yaver/go-staticcheck.md
What go_staticcheck does on Yaver
AI agents invoke go_staticcheck 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why go_staticcheck is rated High
This tool triggers execution of the staticcheck static analysis tool on code, which is an external operation whose effects depend on the arguments provided (which code/paths to analyze). It does not merely read data, but actively executes a subprocess/analysis engine.
From the tool's definition Tool name 'go_staticcheck' and description 'Run staticcheck' indicate execution of an external static analysis tool. 'Run' is an Execute verb, and staticcheck is a Go linting/analysis tool that analyzes code and can report results based on input arguments.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs go_staticcheck 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_staticcheck, this is the rule to start with:
go_staticcheck 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_staticcheck call is checked against it from then on.
Questions about go_staticcheck
Run staticcheck. 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_staticcheck accepts 1 parameter: 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_staticcheck: 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_staticcheck 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_staticcheck 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_staticcheck. 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_staticcheck 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