outlook_move_message · Vibe MCP: Risk & Policy

WHAT IT DOES

What outlook_move_message does on VibeMCP

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

WHY IT NEEDS A POLICY

Why outlook_move_message needs a policy

An AI agent can call outlook_move_message faster than any human can review — one bad instruction and it creates or modifies resources in VibeMCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VibeMCP, so you can run agents against it safely.

FAQ

Questions about outlook_move_message

What does the outlook_move_message tool do? +

Move an Outlook message to a different folder. It is categorised as a Write tool in the VibeMCP 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 Vibe 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 VibeMCP. 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 Vibe MCP server (vibetensor/vibemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.