Create a new Google Doc and optionally insert initial content
AI agents use create_doc to create or update resources in VaultAssist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
The tool creates new data (a Google Doc) in a user's Google Drive, which is a reversible write operation. It does not delete, execute code, move money, or perform irreversible actions. The severity is medium because creating documents could consume storage quota or be used to clutter a workspace, but the impact is limited in scope and reversible through deletion.
From the tool's definition Tool name 'create_doc' and description 'Create a new Google Doc and optionally insert initial content' indicate document creation, which modifies state by adding new data to Google Drive.
Documented attack patterns abuse exactly the kind of access create_doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for create_doc:
{
"version": "1",
"default": "deny",
"tools": {
"create_doc": {
"limits": [
{
"counter": "create_doc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_doc 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 new Google Doc and optionally insert initial content. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for create_doc: 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 VaultAssist. Nothing to install.
create_doc 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 create_doc 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 create_doc. 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.
create_doc is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.