This record as markdown: /tools/io-github-kivanccakmak-yaver/go-mod-graph.md
What go_mod_graph does on Yaver
AI agents call go_mod_graph 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why go_mod_graph is rated Low
The verb 'Show' combined with 'dependency graph' clearly describes a read-only operation that inspects Go module metadata. There are no side effects, no code execution, no data modification, and no destructive operations. This is a standard developer introspection tool with minimal blast radius if misused.
From the tool's definition Tool name 'go_mod_graph' and description 'Show Go module dependency graph' indicate a query/display operation that retrieves and visualizes dependency information without modifying, executing, or deleting any data.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs go_mod_graph 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_mod_graph, this is the rule to start with:
go_mod_graph 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_mod_graph call is checked against it from then on.
Questions about go_mod_graph
Show Go module dependency graph. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
go_mod_graph 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_mod_graph: 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_mod_graph 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_mod_graph 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_mod_graph. 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_mod_graph 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