generate_docs
AI agents use generate_docs to create or update resources in Gworkspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gworkspace environment.
Based on the server's stated capability to manipulate Google Docs and the tool name 'generate_docs', this tool most likely creates or modifies documents (Write category). The absence of a specific tool description reduces confidence, but the parent server's documented Docs manipulation capability and the generative nature of the name ('generate') indicate document creation.
From the tool's definition Tool name 'generate_docs' combined with server description stating it 'enables users to manipulate...Docs...directly from conversational AI interfaces.' The description for this specific tool is empty, limiting certainty.
Attacks that exploit this kind of access
generate_docs. It is categorised as a Write tool in the Gworkspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gworkspace MCP server in PolicyLayer and add a rule for generate_docs: 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 Gworkspace. Nothing to install.
generate_docs 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_docs 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_docs. 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_docs is provided by the Gworkspace MCP server (leoonic/gworkspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →