update_auto_forwarding · Gmail MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_auto_forwarding does on Gmail MCP Server

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

WHY IT NEEDS A POLICY

Why update_auto_forwarding needs a policy

This tool modifies email forwarding rules, which is reversible (settings can be changed back) but has significant security implications. It does not delete data (Destructive), does not move money (Financial), and does not execute arbitrary code (Execute). The 'update' action and focus on configuration changes place it in Write.

From the tool's definition Tool name 'update_auto_forwarding' and description 'Updates automatic forwarding settings' indicate modification of email configuration that controls where messages are automatically sent.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_auto_forwarding Rate-limited

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

FAQ

Questions about update_auto_forwarding

What does the update_auto_forwarding tool do? +

Updates automatic forwarding settings. It is categorised as a Write tool in the Gmail 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 update_auto_forwarding? +

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

What risk level is update_auto_forwarding? +

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

Can I rate-limit update_auto_forwarding? +

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

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

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