archive_email · Google Workspace MCP Server MCP

WHAT IT DOES

What archive_email does on Google Workspace MCP Server

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

WHY IT NEEDS A POLICY

Why archive_email needs a policy

Archiving is a write operation that modifies email status/location but remains reversible (emails can be unarchived). It does not delete data permanently (would be Destructive), nor does it execute external code or access financial systems. The severity is medium because an AI agent systematically archiving emails could disrupt user workflow or hide important messages, but the action is reversible.

From the tool's definition Tool name 'archive_email' and description 'Archive an email' indicate a modification operation on email data. Archiving moves an email from inbox to archive—a reversible action that changes the state of data without permanent deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_email Rate-limited

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

FAQ

Questions about archive_email

What does the archive_email tool do? +

Archive an email. It is categorised as a Write tool in the Google Workspace 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 archive_email? +

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

What risk level is archive_email? +

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

Can I rate-limit archive_email? +

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

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

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