import_markdown
REPLACES the ENTIRE document content with the given Markdown via Drive conversion — the Markdown round-trip writer paired with export_document format=markdown. Supported Markdown (headings, bold/italic/strikethrough, links, ordered/unordered lists, tables, code blocks, images by URL) becomes nati...
This record as markdown: /tools/a1-x-tech-mcp-google-docs/import-markdown.md
What import_markdown does on Mcp Google Docs
AI agents use import_markdown to create or update resources in Mcp Google Docs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Docs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
markdown | string | Yes | The full new document content as Markdown. |
document_id | string | Yes | The document id — the long id from the document URL (docs.google.com/document/d/<documentId>/edit) or from create_document output. |
Parameters from the server's own tool schema.
Why import_markdown is rated Medium
An AI agent can call import_markdown faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Docs by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs import_markdown safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_markdown, this is the rule to start with:
import_markdown 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Docs, apply this rule, and every import_markdown call is checked against it from then on.
Questions about import_markdown
REPLACES the ENTIRE document content with the given Markdown via Drive conversion — the Markdown round-trip writer paired with export_document format=markdown. Supported Markdown (headings, bold/italic/strikethrough, links, ordered/unordered lists, tables, code blocks, images by URL) becomes native Docs formatting. Everything not expressed in the Markdown is LOST: existing text, comment anchors (comments survive but detach), positioned objects, headers/footers and extra tabs. For surgical edits use replace_range/style tools instead. Returns the Drive file resource (id, name, modifiedTime). It is categorised as a Write tool in the Mcp Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
import_markdown accepts 2 parameters: markdown, document_id. Required: markdown, document_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for import_markdown: 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 Google Docs. Nothing to install.
import_markdown 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 import_markdown 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 import_markdown. 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.
import_markdown is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Docs, and thousands of servers like it.
This server
Across the catalogue