Creates comprehensive documentation for code, APIs, or systems. Follows industry best practices for technical documentation. Includes examples, diagrams, and user guides. Uses the configured Vertex AI model (${modelIdPlaceholder}) with Google Search. Requires
AI agents use documentation_generator to create or update resources in Vertex AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vertex AI MCP Server environment.
This tool generates and creates documentation artifacts. Creating new content (documentation files, guides, diagrams) is a Write operation. It does not execute code, delete data, or involve financial transactions. Severity is medium because an AI agent could generate incorrect, misleading, or confidential-leaking documentation at scale, but the blast radius is limited compared to destructive or financial actions.
From the tool's definition 'Creates comprehensive documentation for code, APIs, or systems' and 'Includes examples, diagrams, and user guides'
Documented attack patterns abuse exactly the kind of access documentation_generator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vertex AI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for documentation_generator:
{
"version": "1",
"default": "deny",
"tools": {
"documentation_generator": {
"limits": [
{
"counter": "documentation_generator_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}documentation_generator 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.
Creates comprehensive documentation for code, APIs, or systems. Follows industry best practices for technical documentation. Includes examples, diagrams, and user guides. Uses the configured Vertex AI model (${modelIdPlaceholder}) with Google Search. Requires. It is categorised as a Write tool in the Vertex AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vertex AI MCP Server MCP server in PolicyLayer and add a rule for documentation_generator: 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 Vertex AI MCP Server. Nothing to install.
documentation_generator 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 documentation_generator 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 documentation_generator. 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.
documentation_generator is provided by the Vertex AI MCP Server MCP server (shariqriazz/vertex-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Vertex AI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 Vertex AI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.