// SCAN REPORT

MessengerFlow MCP Server

5 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

4 can modify or destroy data

1 read-only

5 tools total

Community server · catalogue entry verified 30/06/2026

How to control MessengerFlow MCP Server ↓

TOOL MAP

What MessengerFlow MCP Server exposes to your agents

Read (1) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MessengerFlow MCP Server tools

Write · High manage_accounts While the tool includes delete functionality (which would typically be Destructive), the description frames it as account management with add/update/delete as coordinate operations. Write · High manage_campaigns Although the tool includes delete operations which could warrant a Destructive classification, the description emphasizes create, update, and state management (start/stop) as primary functions. Write · High manage_inbox While the tool includes a destructive capability (deleting conversations), the core functionality described emphasizes write operations: sending replies and marking messages. Write · High manage_leads While 'delete' appears in the description, the overall tool design emphasizes creating, organizing, and modifying lead collections (import, scrape, merge, rename).

4 of MessengerFlow MCP Server's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MessengerFlow MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and MessengerFlow MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "manage_accounts": {
    "limits": [
      {
        "counter": "manage_accounts_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_analytics": {
    "limits": [
      {
        "counter": "get_analytics_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MessengerFlow MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MESSENGERFLOW →

Instant setup, no code required.

FULL CATALOGUE

All 5 MessengerFlow MCP Server tools

WRITE 4 tools

Write manage_accounts Add, update, and delete Facebook accounts. View account stats and logs. Write manage_campaigns Create, update, start, stop, and delete campaigns. View campaign leads and activity. Manage campaign account a Write manage_inbox View conversations, search messages, send replies, mark read/unread, and delete conversations. Write manage_leads Manage lead collections — import CSV, scrape groups/pages, merge, rename, delete, export. Browse individual le

READ 1 tools

Read get_analytics Get dashboard stats, activity charts, performance metrics, and message/booking charts.

FAQ

Questions about MessengerFlow MCP Server

How do I prevent bulk modifications through MessengerFlow MCP Server? +

The MessengerFlow MCP Server server has 4 write tools including manage_accounts, manage_campaigns, manage_inbox. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MessengerFlow MCP Server.

How many tools does the MessengerFlow MCP Server MCP server expose? +

5 tools across 2 categories: Read, Write. 1 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on MessengerFlow MCP Server? +

Register the MessengerFlow MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MessengerFlow MCP Server tool call.

Deterministic rules across all 5 MessengerFlow MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MESSENGERFLOW →

Instant setup, no code required.

5 MessengerFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.