manage_leads · MessengerFlow MCP Server MCP: Risk & Policy

WHAT IT DOES

What manage_leads does on MessengerFlow MCP Server

AI agents use manage_leads 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_leads needs a policy

While 'delete' appears in the description, the overall tool design emphasizes creating, organizing, and modifying lead collections (import, scrape, merge, rename). These are reversible write operations. The 'delete' likely refers to removing leads from collections or collections themselves, which is less severe than destroying customer records permanently.

From the tool's definition Tool performs reversible operations: 'import CSV, scrape groups/pages, merge, rename' modify lead data. The 'delete' operation is destructive but contextually refers to lead collection management (renaming collections, not destroying irreplaceable customer…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_leads Rate-limited

manage_leads 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_leads": {
      "limits": [
        {
          "counter": "manage_leads_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_leads

What does the manage_leads tool do? +

Manage lead collections — import CSV, scrape groups/pages, merge, rename, delete, export. Browse individual leads within a collection. 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_leads? +

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

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

Can I rate-limit manage_leads? +

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

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

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