Move emails to a specified folder using UIDs. UIDs are permanent identifiers. Use list_folders to see available folders.
AI agents use move_emails to create or update resources in Yahoo Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yahoo Mail environment.
Moving emails changes their mailbox location and organizational metadata, which is a data modification operation. While reversible, this is more impactful than simple reads (like list_emails or read_email) and constitutes a write operation. It is not destructive because emails are not removed from the system.
From the tool's definition Tool description states 'Move emails to a specified folder' — this modifies the organizational state and location of emails without deleting them. The capability is reversible (emails can be moved back), distinguishing it from destructive deletion.
Documented attack patterns abuse exactly the kind of access move_emails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yahoo Mail, and nothing reaches the server without passing your rules. This is the rule we recommend for move_emails:
{
"version": "1",
"default": "deny",
"tools": {
"move_emails": {
"limits": [
{
"counter": "move_emails_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_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.
Free to start. No card required.
Move emails to a specified folder using UIDs. UIDs are permanent identifiers. Use list_folders to see available folders. It is categorised as a Write tool in the Yahoo Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yahoo Mail MCP server in PolicyLayer and add a rule for move_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 Yahoo Mail. Nothing to install.
move_emails 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_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.
Set action: deny in the PolicyLayer policy for move_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.
move_emails is provided by the Yahoo Mail MCP server (jtokib/yahoo-mail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yahoo Mail, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Yahoo Mail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.