This record as markdown: /tools/esanum-mcp-mautic/mautic-get-campaign.md
What mautic_get_campaign does on Mcp Mautic
AI agents call mautic_get_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.
Why mautic_get_campaign is rated Low
The tool retrieves campaign information by ID, which is a read-only query operation. It does not create, modify, delete, or execute any actions. There is no data mutation or external operation triggered. The blast radius of misuse is minimal—an AI agent could only access campaign data it has ID access to, which is expected in a marketing automation context.
From the tool's definition Tool name 'mautic_get_campaign' combined with description 'Get campaign by ID' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs mautic_get_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_get_campaign, this is the rule to start with:
mautic_get_campaign is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Mautic, apply this rule, and every mautic_get_campaign call is checked against it from then on.
Questions about mautic_get_campaign
Get campaign by ID. It is categorised as a Read tool in the Mcp Mautic MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_get_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.
mautic_get_campaign is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mautic_get_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.
Set action: deny in the PolicyLayer policy for mautic_get_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.
mautic_get_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.
More on Mcp Mautic, and thousands of servers like it.
This server
Across the catalogue