outlook_move_message

Move an email message to a different mail folder.

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/outlook-move-message.md

WHAT IT DOES

What outlook_move_message does on Sage MCP

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

RISK

Why outlook_move_message is rated Medium

Moving an email to a different folder modifies the message's organizational state and is reversible (can be moved back). This constitutes a Write operation rather than Read (which would only retrieve data) or Destructive (which would permanently delete).

From the tool's definition Tool name 'outlook_move_message' and description 'Move an email message to a different mail folder' indicate modification of email state by relocating messages between folders.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs outlook_move_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For outlook_move_message, this is the rule to start with:

outlook_move_message Rate-limited

outlook_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": {
    "outlook_move_message": {
      "limits": [
        {
          "counter": "outlook_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 Sage MCP, apply this rule, and every outlook_move_message call is checked against it from then on.

FAQ

Questions about outlook_move_message

What does the outlook_move_message tool do? +

Move an email message to a different mail folder. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on outlook_move_message? +

Register the Sage MCP server in PolicyLayer and add a rule for outlook_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 Sage MCP. Nothing to install.

What risk level is outlook_move_message? +

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

Can I rate-limit outlook_move_message? +

Yes. Add a rate_limit block to the outlook_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 outlook_move_message completely? +

Set action: deny in the PolicyLayer policy for outlook_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 outlook_move_message? +

outlook_move_message is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

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

Guides

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