execute_migration_move · GAM MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_migration_move does on GAM MCP Server

AI agents invoke execute_migration_move to trigger actions in GAM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_migration_move needs a policy

The 'execute_' prefix indicates this triggers an operation rather than passive retrieval. 'migration_move' suggests moving data between locations or organizational units in Google Workspace, which is a consequential action.

From the tool's definition Tool named 'execute_migration_move' with empty description. Context indicates it operates within GAM7 for Google Workspace administration, managing users, groups, calendar, and Drive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_migration_move Rate-limited

execute_migration_move stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_migration_move": {
      "limits": [
        {
          "counter": "execute_migration_move_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about execute_migration_move

What does the execute_migration_move tool do? +

execute_migration_move. It is categorised as a Execute tool in the GAM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_migration_move? +

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

What risk level is execute_migration_move? +

execute_migration_move is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_migration_move? +

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

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

execute_migration_move is provided by the GAM MCP Server MCP server (ktibbs9417/gamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.