doc
Generates Rust documentation and returns structured output with warning count.
This record as markdown: /tools/io-github-dave-london-go/doc.md
What doc does on Go
AI agents call doc to retrieve information from Go without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why doc is rated Low
The 'doc' tool generates documentation artifacts and diagnostic warnings, which is a data retrieval and reporting operation. It has no side effects, does not execute arbitrary code, does not create/modify/delete persistent data, and does not involve financial operations. This fits cleanly into the Read category as a documentation generation and diagnostic reporting tool.
From the tool's definition Tool generates documentation and returns structured output with warning count. The description indicates a read-only operation that produces diagnostic information without modifying code, configuration, or external systems.
Attacks that exploit this kind of access
The rule that runs doc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For doc, this is the rule to start with:
doc 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 Go, apply this rule, and every doc call is checked against it from then on.
Questions about doc
Generates Rust documentation and returns structured output with warning count. It is categorised as a Read tool in the Go MCP Server, which means it retrieves data without modifying state.
Register the Go MCP server in PolicyLayer and add a rule for doc: 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 Go. Nothing to install.
doc 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 doc 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 doc. 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.
doc is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue