mail_move_message
Move an email message to a different mailbox/folder.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/mail-move-message.md
What mail_move_message does on AIquila — Nextcloud MCP Server
AI agents use mail_move_message to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
messageId | number | Yes | The message ID to move |
destMailboxId | number | Yes | The destination mailbox ID (from list_mailboxes) |
Parameters from the server's own tool schema.
Why mail_move_message is rated Medium
Moving an email message modifies its location but is reversible—the message remains intact and can be moved back to its original folder. This is a write operation (state change) rather than destructive (no deletion) or execute (no code/command execution).
From the tool's definition Tool name 'mail_move_message' and description 'Move an email message to a different mailbox/folder' indicate modification of message state/location.
Attacks that exploit this kind of access
The rule that runs mail_move_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_move_message, this is the rule to start with:
mail_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 AIquila — Nextcloud MCP Server, apply this rule, and every mail_move_message call is checked against it from then on.
Questions about mail_move_message
Move an email message to a different mailbox/folder. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mail_move_message accepts 2 parameters: messageId, destMailboxId. Required: messageId, destMailboxId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for mail_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 AIquila — Nextcloud MCP Server. Nothing to install.
mail_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 mail_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 mail_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.
mail_move_message is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue