doc
Generates Rust documentation and returns structured output with warning count.
This record as markdown: /tools/io-github-dave-london-pare-test/doc.md
What doc does on Test
AI agents invoke doc to trigger actions in Test. 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.
Why doc is rated High
Generating documentation runs an external build/doc tool (e.g., `cargo doc`) as a subprocess. This is an execution of an external command/process rather than a simple read or write operation. Misuse could trigger unintended build processes or expose build artifacts, hence medium severity.
From the tool's definition Generates Rust documentation
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 Test, 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 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 Test, 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 Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test 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 Test. Nothing to install.
doc 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 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 Test 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 Test, and thousands of servers like it.
This server
Across the catalogue