mautic_export_campaign

Export a campaign as JSON including all events, actions, decisions, and connections. Useful for backup, migration between environments, or templating.

SERVERMcp Mautic SOURCEesanum/mcp-mautic

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/esanum-mcp-mautic/mautic-export-campaign.md

WHAT IT DOES

What mautic_export_campaign does on Mcp Mautic

AI agents call mautic_export_campaign to retrieve information from Mcp Mautic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mautic_export_campaign is rated Low

The tool exports/retrieves campaign data as JSON. This is a read operation — it queries and returns existing campaign configuration without modifying or deleting any data. The use cases listed (backup, migration, templating) confirm it is non-destructive and read-only. Severity is low as it only reads campaign configuration data.

From the tool's definition Export a campaign as JSON including all events, actions, decisions, and connections. Useful for backup, migration between environments, or templating.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mautic_export_campaign safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Mautic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mautic_export_campaign, this is the rule to start with:

mautic_export_campaign Allowed

mautic_export_campaign is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mautic_export_campaign": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Mautic, apply this rule, and every mautic_export_campaign call is checked against it from then on.

FAQ

Questions about mautic_export_campaign

What does the mautic_export_campaign tool do? +

Export a campaign as JSON including all events, actions, decisions, and connections. Useful for backup, migration between environments, or templating. It is categorised as a Read tool in the Mcp Mautic MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mautic_export_campaign? +

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

What risk level is mautic_export_campaign? +

mautic_export_campaign is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mautic_export_campaign? +

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

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

mautic_export_campaign is provided by the Mcp Mautic MCP server (esanum/mcp-mautic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Mautic, and thousands of servers like it.

This server

All 229 Mcp Mautic tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →