export_emails

A write tool on the Cowork Bench MCP server.

SERVERCowork Bench SOURCE0717376/cowork_bench

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/cowork-bench/export-emails.md

WHAT IT DOES

What export_emails does on Cowork Bench

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

RISK

Why export_emails is rated Medium

An AI agent can call export_emails faster than any human can review: one bad instruction and it creates or modifies resources in Cowork Bench by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_emails safely

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

export_emails Rate-limited

export_emails 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": {
    "export_emails": {
      "limits": [
        {
          "counter": "export_emails_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 Cowork Bench, apply this rule, and every export_emails call is checked against it from then on.

FAQ

Questions about export_emails

What does the export_emails tool do? +

export_emails is a write tool on the Cowork Bench MCP server. It is categorised as a Write tool in the Cowork Bench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_emails? +

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

What risk level is export_emails? +

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

Can I rate-limit export_emails? +

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

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

export_emails is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench tools →

Across the catalogue

The MCP Attack Database →

Guides

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