drive_bulk_move · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What drive_bulk_move does on TrekMail MCP Server

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

WHY IT NEEDS A POLICY

Why drive_bulk_move needs a policy

This tool modifies the structural location of files and folders by changing their parent directory/folder, which is a reversible write operation. While it affects multiple items (bulk operation), the changes are not destructive—items are moved, not deleted, and the operation can be undone by moving items back.

From the tool's definition Tool description states "Re-parent N items to target_folder_id" and mentions "Files use a single UPDATE; folders go one-by-one". The use of UPDATE operations and re-parenting (moving items between locations) indicates data modification.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_bulk_move Rate-limited

drive_bulk_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_bulk_move": {
      "limits": [
        {
          "counter": "drive_bulk_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 TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_bulk_move

What does the drive_bulk_move tool do? +

Re-parent N items to target_folder_id (null = root). Files use a single UPDATE; folders go one-by-one for cycle detection. It is categorised as a Write tool in the TrekMail MCP Server 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_bulk_move? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_bulk_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 TrekMail MCP Server. Nothing to install.

What risk level is drive_bulk_move? +

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

Can I rate-limit drive_bulk_move? +

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

Set action: deny in the PolicyLayer policy for drive_bulk_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_bulk_move? +

drive_bulk_move is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.