email_move_message
Move an email message to a different mailbox/folder
This record as markdown: /tools/io-github-alifanov-scopegate/email-move-message.md
What email_move_message does on ScopeGate
AI agents use email_move_message to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why email_move_message is rated Medium
Moving an email is a reversible write operation that changes the location/state of data (mailbox/folder assignment) without permanently deleting it. The agent could misuse this to reorganize, hide, or misfiled sensitive emails, causing confusion or loss of discoverability. This is less severe than deletion (Destructive) but represents data modification with potential for user confusion or compliance issues.
From the tool's definition Tool name 'email_move_message' and description 'Move an email message to a different mailbox/folder' indicate modification of email organization state.
Attacks that exploit this kind of access
The rule that runs email_move_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_move_message, this is the rule to start with:
email_move_message 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 ScopeGate, apply this rule, and every email_move_message call is checked against it from then on.
Questions about email_move_message
Move an email message to a different mailbox/folder. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for email_move_message: 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 ScopeGate. Nothing to install.
email_move_message 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 email_move_message 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 email_move_message. 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.
email_move_message is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue