drive_move · Gworkspace MCP: Risk & Policy

WHAT IT DOES

What drive_move does on Gworkspace

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

WHY IT NEEDS A POLICY

Why drive_move needs a policy

Moving a file changes its organizational state (parent folder) but does not delete or destroy data, making it Write rather than Destructive. The blast radius is medium because an AI agent could relocate critical files into inaccessible folders or disrupt organizational structure, but the action remains reversible—files can be moved back.

From the tool's definition Tool description states 'Move a file to a different folder' - this modifies file location metadata within Google Drive, which is a reversible state change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_move Rate-limited

drive_move 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_move": {
      "limits": [
        {
          "counter": "drive_move_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 Gworkspace, so you can run agents against it safely.

FAQ

Questions about drive_move

What does the drive_move tool do? +

Move a file to a different folder. It is categorised as a Write tool in the Gworkspace 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_move? +

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

What risk level is drive_move? +

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

Can I rate-limit drive_move? +

Yes. Add a rate_limit block to the drive_move 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_move completely? +

Set action: deny in the PolicyLayer policy for drive_move. 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_move? +

drive_move is provided by the Gworkspace MCP server (leoonic/gworkspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.