Create a new file in Google Drive, with content or from a URL
AI agents use create_drive_file 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.
This tool creates new files in Google Drive, which is a reversible Write operation. While it adds data to a user's account, the action can be undone by deletion. The severity is medium because an agent misusing this tool could create many files or files with sensitive/malicious content, consuming storage and potentially introducing security risks, but the primary concern is data creation rather than destruction or…
From the tool's definition Tool name 'create_drive_file' and description 'Create a new file in Google Drive, with content or from a URL' indicate creation of new data in a user's storage without deletion or overwriting.
Documented attack patterns abuse exactly the kind of access create_drive_file 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_drive_file:
{
"version": "1",
"default": "deny",
"tools": {
"create_drive_file": {
"limits": [
{
"counter": "create_drive_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_drive_file 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 file in Google Drive, with content or from a URL. 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_drive_file: 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_drive_file 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_drive_file 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_drive_file. 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_drive_file 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.