Generates Rust documentation and returns structured output with warning count.
AI agents invoke doc to trigger actions in Make. 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.
Running a documentation generator like `cargo doc` executes an external process/command on the system. While it is typically read-only in terms of source code, it triggers execution of a build tool, compiles code metadata, and writes output artifacts to disk. The most accurate category is Execute due to the external process invocation.
From the tool's definition Generates Rust documentation — this runs a documentation generation process (e.g., `cargo doc`), which executes an external build/toolchain command
Documented attack patterns abuse exactly the kind of access doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for doc:
{
"version": "1",
"default": "deny",
"tools": {
"doc": {
"limits": [
{
"counter": "doc_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Generates Rust documentation and returns structured output with warning count. It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Make 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 Make. 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 Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.