doc
Generates Rust documentation and returns structured output with warning count.
This record as markdown: /tools/io-github-dave-london-lint/doc.md
What doc does on Lint
AI agents call doc to retrieve information from Lint 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
This is a documentation generation tool that analyzes Rust code and produces diagnostic output. It is informational only - it queries/analyzes existing code and returns structured results without side effects. The tool does not modify, delete, or execute code, making it a Read operation with low severity. Misuse would result in unwanted documentation generation or information disclosure at worst.
From the tool's definition Tool 'doc' generates documentation and returns structured output with warning count. It reads source code to produce documentation output with no modification to source files, deletion, execution of arbitrary code, or financial operations.
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 Lint, 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 Lint, 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 Lint MCP Server, which means it retrieves data without modifying state.
Register the Lint 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 Lint. 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 Lint 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 Lint, and thousands of servers like it.
This server
Across the catalogue