AI agents use generate_documentation to create or update resources in Mcp Llm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Llm environment.
This tool creates new documentation content, which is a reversible Write operation. It does not retrieve data (Read), execute arbitrary code (Execute), delete anything (Destructive), or move money (Financial). However, without explicit confirmation that it writes to files, and given the description is relatively minimal, confidence is moderate rather than high.
From the tool's definition Tool description states it will "Generate documentation for code", which creates new content (documentation files or outputs).
Documented attack patterns abuse exactly the kind of access generate_documentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Llm, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"generate_documentation": {
"limits": [
{
"counter": "generate_documentation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_documentation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate documentation for code. It is categorised as a Write tool in the Mcp Llm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Llm MCP server in PolicyLayer and add a rule for generate_documentation: 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 Mcp Llm. Nothing to install.
generate_documentation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_documentation 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 generate_documentation. 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.
generate_documentation is provided by the Mcp Llm MCP server (sammcj/mcp-llm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Mcp Llm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Mcp Llm tools catalogued and risk-classified — across an index of 42,500+ MCP servers.