Create a Google Doc from HTML content in a single Drive API call. HTML tags are converted to native Google Doc styles: <h1> → Heading 1, <h2> → Heading 2, <p> → Normal Text, <b> → bold, <i> → italic, <ul>/<ol> → lists, <table> → tables. Useful when you want native heading/list/table styling appli...
AI agents use createDocFromHTML to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.
This tool creates a new Google Doc (reversible write operation). While document creation is not destructive, it does generate new persistent data in a user's Drive. The severity is medium rather than low because an AI agent could create numerous documents, consume quota, or generate unwanted content that clutters user storage—though the action remains reversible via deletion.
From the tool's definition Tool description states it will 'Create a Google Doc from HTML content' and explicitly describes formatting conversions applied to the document structure, indicating document creation/modification.
Documented attack patterns abuse exactly the kind of access createDocFromHTML gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Drive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for createDocFromHTML:
{
"version": "1",
"default": "deny",
"tools": {
"createDocFromHTML": {
"limits": [
{
"counter": "createdocfromhtml_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createDocFromHTML 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.
Create a Google Doc from HTML content in a single Drive API call. HTML tags are converted to native Google Doc styles: <h1> → Heading 1, <h2> → Heading 2, <p> → Normal Text, <b> → bold, <i> → italic, <ul>/<ol> → lists, <table> → tables. Useful when you want native heading/list/table styling applied in one request instead of a createGoogleDoc call followed by per-paragraph formatGoogleDocParagraph requests. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for createDocFromHTML: 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 Google Drive MCP Server. Nothing to install.
createDocFromHTML 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 createDocFromHTML 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 createDocFromHTML. 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.
createDocFromHTML is provided by the Google Drive MCP Server MCP server (piotr-agier/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 107 Google Drive MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
107 Google Drive MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.