email_archive

Archive an email message (removes from inbox). Subject to mailbox grant permissions.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/email-archive.md

WHAT IT DOES

What email_archive does on FlowDot MCP Server

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

RISK

Why email_archive is rated Medium

This tool modifies email state by moving a message from inbox to archive, which is a reversible action (emails can be unarchived). While it alters data, it does not permanently delete it, making it Write rather than Destructive. The mention of 'removes from inbox' indicates a state change operation.

From the tool's definition Archive an email message (removes from inbox). Subject to mailbox grant permissions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_archive safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_archive, this is the rule to start with:

email_archive Rate-limited

email_archive 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": {
    "email_archive": {
      "limits": [
        {
          "counter": "email_archive_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every email_archive call is checked against it from then on.

FAQ

Questions about email_archive

What does the email_archive tool do? +

Archive an email message (removes from inbox). Subject to mailbox grant permissions. It is categorised as a Write tool in the FlowDot 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 email_archive? +

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

What risk level is email_archive? +

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

Can I rate-limit email_archive? +

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

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

email_archive is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

forward-email on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →