move_to_inbox · Google Connections MCP: Risk & Policy

WHAT IT DOES

What move_to_inbox does on Google Connections

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

WHY IT NEEDS A POLICY

Why move_to_inbox needs a policy

Moving messages to inbox is a write operation that changes message metadata (folder/label assignments) but is fully reversible — messages can be moved back out or to other folders. While it could be misused to suppress important messages or manipulate an inbox, the effect is not destructive (messages are not deleted) and the action can be undone.

From the tool's definition Tool name is 'move_to_inbox' and description states 'Move one or more Gmail messages to inbox' — this modifies the state/labels of Gmail messages by changing their folder/label status, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_to_inbox Rate-limited

move_to_inbox 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": {
    "move_to_inbox": {
      "limits": [
        {
          "counter": "move_to_inbox_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 Google Connections, so you can run agents against it safely.

FAQ

Questions about move_to_inbox

What does the move_to_inbox tool do? +

Move one or more Gmail messages to inbox. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_to_inbox? +

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

What risk level is move_to_inbox? +

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

Can I rate-limit move_to_inbox? +

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

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

move_to_inbox is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.