This record as markdown: /tools/cowork-bench/move-email.md
What move_email does on Cowork Bench
AI agents use move_email 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.
Why move_email is rated Medium
Moving an email changes its location/folder assignment but does not delete or irreversibly destroy data. This is a write operation (data modification) rather than destructive. Severity is medium due to potential for misuse (moving sensitive emails to inaccessible folders, organizational disruption) but the action is reversible. Confidence is high given the clear, descriptive name and straightforward operation.
From the tool's definition Tool performs 'Move email to another folder' - a reversible modification of email state/organization without deletion or destruction
Attacks that exploit this kind of access
The rule that runs move_email 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 move_email, this is the rule to start with:
move_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every move_email call is checked against it from then on.
Questions about move_email
Move email to another folder. 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.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for move_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 Cowork Bench. Nothing to install.
move_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_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.
Set action: deny in the PolicyLayer policy for move_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.
move_email 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.
More on Cowork Bench, and thousands of servers like it.
This server
Across the catalogue