manage_accounts · MessengerFlow MCP Server MCP

WHAT IT DOES

What manage_accounts does on MessengerFlow MCP Server

AI agents use manage_accounts 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_accounts needs a policy

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. The severity is high because misconfigured deletion of Facebook accounts could cause significant business disruption, loss of marketing campaign infrastructure, and customer relationship damage.

From the tool's definition Tool description states 'Add, update, and delete Facebook accounts.' The delete operation is destructive, but the tool's primary framing emphasizes account management (add, update, delete) as a collective Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_accounts Rate-limited

manage_accounts 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_accounts": {
      "limits": [
        {
          "counter": "manage_accounts_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_accounts

What does the manage_accounts tool do? +

Add, update, and delete Facebook accounts. View account stats and logs. 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_accounts? +

Register the MessengerFlow MCP Server MCP server in PolicyLayer and add a rule for manage_accounts: 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_accounts? +

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

Can I rate-limit manage_accounts? +

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

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

manage_accounts 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.