This record as markdown: /tools/io-github-kivanccakmak-yaver/go-module-info.md
What go_module_info does on Yaver
AI agents call go_module_info to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
module | string | Yes | e.g. github.com/gin-gonic/gin |
Parameters from the server's own tool schema.
Why go_module_info is rated Low
This tool retrieves information about Go modules from the official Go module proxy without modifying any data, executing code, or causing side effects. It is a straightforward query operation analogous to 'get' or 'fetch', placing it firmly in the Read category. Severity is low because the data source is public and read-only, limiting potential harm from misuse.
From the tool's definition Tool description states 'Get Go module info from proxy.golang.org' — a read-only retrieval operation querying public module metadata
Attacks that exploit this kind of access
The rule that runs go_module_info 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_module_info, this is the rule to start with:
go_module_info is read-only, so it stays allowed. 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_module_info call is checked against it from then on.
Questions about go_module_info
Get Go module info from proxy.golang.org. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
go_module_info accepts 1 parameter: module. Required: module. 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_module_info: 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_module_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the go_module_info 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_module_info. 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_module_info 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.
This server
Across the catalogue