move_message

Move a message to another mailbox.

SERVERIconnect SOURCEiconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/move-message.md

WHAT IT DOES

What move_message does on Iconnect

AI agents use move_message to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.

RISK

Why move_message is rated Medium

Moving a message between mailboxes is a reversible modification of message metadata/organization. It is not a read-only operation (category Read), as it changes message state. It is not destructive, since the message is not deleted or purged. It is not an execute operation that runs arbitrary code. It is not financial. Therefore, Write is the appropriate category.

From the tool's definition Tool description states 'Move a message to another mailbox.' Moving a message modifies its location/state within the mail system, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_message": {
      "limits": [
        {
          "counter": "move_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every move_message call is checked against it from then on.

FAQ

Questions about move_message

What does the move_message tool do? +

Move a message to another mailbox. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_message? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is move_message? +

move_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_message? +

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.

How do I block move_message completely? +

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.

What MCP server provides move_message? +

move_message is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →