mautic_delete_user

Delete a Mautic user

SERVERMcp Mautic SOURCEesanum/mcp-mautic

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/esanum-mcp-mautic/mautic-delete-user.md

WHAT IT DOES

What mautic_delete_user does on Mcp Mautic

AI agents call mautic_delete_user to permanently remove resources in Mcp Mautic, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mautic_delete_user is rated Critical

Deleting a user account is an irreversible action that removes user data and access. This causes permanent loss of identity/credentials and cannot be undone without restoration from backups. While not directly financial, the impact is severe in a marketing automation system where user accounts control campaign management and contact data access.

From the tool's definition Tool name: 'mautic_delete_user' with description 'Delete a Mautic user'. The verb 'delete' is explicitly destructive and irreversible.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mautic_delete_user 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_delete_user, this is the rule to start with:

mautic_delete_user Hidden

mautic_delete_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "mautic_delete_user"
  ]
}

RESTRICT 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_delete_user call is checked against it from then on.

FAQ

Questions about mautic_delete_user

What does the mautic_delete_user tool do? +

Delete a Mautic user. It is categorised as a Destructive tool in the Mcp Mautic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mautic_delete_user? +

Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_delete_user: 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_delete_user? +

mautic_delete_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mautic_delete_user? +

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

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

mautic_delete_user 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 → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →