This record as markdown: /tools/heznpc-airmcp/move-message.md
What move_message does on AirMCP
AI agents use move_message to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why move_message is rated Medium
This tool creates or modifies data reversibly by relocating messages between mailboxes without deleting them. It falls under Write rather than Destructive because the operation is fully reversible—messages remain intact and can be moved again.
From the tool's definition Tool name 'move_message' and description 'Move a message to another mailbox' indicate the tool modifies message location/state within Mail. Moving messages is a reversible operation (messages can be moved back or to other folders).
Attacks that exploit this kind of access
The rule that runs move_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_message, this is the rule to start with:
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 AirMCP, apply this rule, and every move_message call is checked against it from then on.
Questions about move_message
Move a message to another mailbox. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for 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 AirMCP. Nothing to install.
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 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 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.
move_message is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue