manage_inbox · MessengerFlow MCP Server MCP: Risk & Policy

WHAT IT DOES

What manage_inbox does on MessengerFlow MCP Server

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

WHY IT NEEDS A POLICY

Why manage_inbox needs a policy

While the tool includes a destructive capability (deleting conversations), the core functionality described emphasizes write operations: sending replies and marking messages. However, the deletion component elevates risk.

From the tool's definition Tool description states it can 'send replies, mark read/unread, and delete conversations.' The 'delete conversations' capability is destructive, but the primary documented functions are write operations ('send replies,' 'mark read/unread').

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_inbox Rate-limited

manage_inbox 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": {
    "manage_inbox": {
      "limits": [
        {
          "counter": "manage_inbox_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 MessengerFlow MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_inbox

What does the manage_inbox tool do? +

View conversations, search messages, send replies, mark read/unread, and delete conversations. It is categorised as a Write tool in the MessengerFlow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_inbox? +

Register the MessengerFlow MCP Server MCP server in PolicyLayer and add a rule for manage_inbox: 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 MessengerFlow MCP Server. Nothing to install.

What risk level is manage_inbox? +

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

Can I rate-limit manage_inbox? +

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

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

manage_inbox is provided by the MessengerFlow MCP Server MCP server (messengerflow/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.