drive_upload · Hermes Google MCP: Risk & Policy

WHAT IT DOES

What drive_upload does on Hermes Google

AI agents use drive_upload to create or update resources in Hermes Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hermes Google environment.

WHY IT NEEDS A POLICY

Why drive_upload needs a policy

This tool creates or modifies data on Google Drive by uploading files. It is reversible (files can be deleted), so it does not qualify as Destructive. The user confirmation requirement reduces blast radius from high to medium, as it provides a control gate against accidental misuse. No financial, code execution, or arbitrary command aspects apply.

From the tool's definition Tool name 'drive_upload' and description 'Upload a local file to Drive' indicate file creation/modification on Google Drive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_upload Rate-limited

drive_upload 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_upload": {
      "limits": [
        {
          "counter": "drive_upload_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hermes Google, so you can run agents against it safely.

FAQ

Questions about drive_upload

What does the drive_upload tool do? +

Upload a local file to Drive. Requires user confirmation before calling. It is categorised as a Write tool in the Hermes Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drive_upload? +

Register the Hermes Google MCP server in PolicyLayer and add a rule for drive_upload: 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 Hermes Google. Nothing to install.

What risk level is drive_upload? +

drive_upload is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit drive_upload? +

Yes. Add a rate_limit block to the drive_upload 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.

How do I block drive_upload completely? +

Set action: deny in the PolicyLayer policy for drive_upload. 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.

What MCP server provides drive_upload? +

drive_upload is provided by the Hermes Google MCP server (jimmy-larsson/hermes-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.