mautic_get_dynamic_content_lead_data
Get per-contact dynamic content personalization data. See which dynamic content was shown to which contacts.
This record as markdown: /tools/esanum-mcp-mautic/mautic-get-dynamic-content-lead-data.md
What mautic_get_dynamic_content_lead_data does on Mcp Mautic
AI agents call mautic_get_dynamic_content_lead_data 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_dynamic_content_lead_data is rated Low
This is a query/retrieval operation that accesses historical records of dynamic content shown to contacts. It has no side effects, does not modify any data, and does not trigger external actions.
From the tool's definition Tool retrieves 'per-contact dynamic content personalization data' and shows 'which dynamic content was shown to which contacts' — pure data retrieval with no modification, creation, deletion, or external execution.
Attacks that exploit this kind of access
The rule that runs mautic_get_dynamic_content_lead_data 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_dynamic_content_lead_data, this is the rule to start with:
mautic_get_dynamic_content_lead_data 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_dynamic_content_lead_data call is checked against it from then on.
Questions about mautic_get_dynamic_content_lead_data
Get per-contact dynamic content personalization data. See which dynamic content was shown to which contacts. 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_dynamic_content_lead_data: 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_dynamic_content_lead_data 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_dynamic_content_lead_data 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_dynamic_content_lead_data. 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_dynamic_content_lead_data 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