Convert an existing PDF in Drive into an editable Google Doc
AI agents use convertPdfToGoogleDoc 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.
Converting a PDF to a Google Doc creates a new file resource and modifies the state of the Drive ecosystem (adding a new document). This is clearly a Write operation—it creates/modifies data reversibly and does not delete, execute arbitrary code, or move funds.
From the tool's definition Tool description states 'Convert an existing PDF in Drive into an editable Google Doc', which creates a new document by transforming an existing file. This is a reversible modification/creation of data within Google Drive.
Documented attack patterns abuse exactly the kind of access convertPdfToGoogleDoc 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 convertPdfToGoogleDoc:
{
"version": "1",
"default": "deny",
"tools": {
"convertPdfToGoogleDoc": {
"limits": [
{
"counter": "convertpdftogoogledoc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convertPdfToGoogleDoc 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.
Convert an existing PDF in Drive into an editable Google Doc. 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 convertPdfToGoogleDoc: 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.
convertPdfToGoogleDoc 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 convertPdfToGoogleDoc 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 convertPdfToGoogleDoc. 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.
convertPdfToGoogleDoc 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.