move_email
AI agents use move_email to create or update resources in AOL Mail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AOL Mail MCP Server environment.
move_email creates or modifies email state (folder location) reversibly—it can be undone by moving the email back. This is a Write-category action, not Destructive (emails remain intact) or Read-only. Severity is medium because misuse could reorganize a user's mailbox, potentially hiding important emails, but the action is reversible and does not permanently delete data or access financial systems.
From the tool's definition Tool name 'move_email' and sibling context (move_all_emails, delete_email, mark_read) indicate email management operations.
Attacks that exploit this kind of access
move_email. It is categorised as a Write tool in the AOL Mail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AOL Mail MCP Server 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 AOL Mail MCP Server. 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 AOL Mail MCP Server MCP server (kubegrind/aol-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →