confirm_bulk_modify · Google MCP: Risk & Policy

WHAT IT DOES

What confirm_bulk_modify does on Google

AI agents invoke confirm_bulk_modify to trigger actions in Google. 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 confirm_bulk_modify needs a policy

This tool executes a bulk email operation, which is an external action that sends emails to potentially many recipients. It is not purely a write (data modification) but triggers an external operation with broad reach. Misuse could result in mass unsolicited emails, making severity high. The word 'execute' in the description directly supports the Execute category.

From the tool's definition "Confirm and execute the prepared bulk email operation"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_bulk_modify Rate-limited

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

FAQ

Questions about confirm_bulk_modify

What does the confirm_bulk_modify tool do? +

✅ Confirm and execute the prepared bulk email operation. It is categorised as a Execute tool in the Google MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on confirm_bulk_modify? +

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

What risk level is confirm_bulk_modify? +

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

Can I rate-limit confirm_bulk_modify? +

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

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

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