custom_delete_user
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-delete-user.md
What custom_delete_user does on Marketo MCP Server
AI agents call custom_delete_user to permanently remove resources in Marketo MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why custom_delete_user is rated Critical
The tool name explicitly contains 'delete' and targets 'user' entities. Deletion operations are irreversible and cannot be undone, placing this in the Destructive category. The critical severity is justified because deleting user/lead records in a marketing automation system constitutes permanent loss of customer data with no recovery mechanism.
From the tool's definition Tool name is 'custom_delete_user' containing 'delete' which indicates irreversible data removal. The description states it 'Calls the Marketo REST API directly' for a delete operation.
Attacks that exploit this kind of access
The rule that runs custom_delete_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Marketo MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For custom_delete_user, this is the rule to start with:
custom_delete_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every custom_delete_user call is checked against it from then on.
Questions about custom_delete_user
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Destructive tool in the Marketo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_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 Marketo MCP Server. Nothing to install.
custom_delete_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the custom_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.
Set action: deny in the PolicyLayer policy for custom_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.
custom_delete_user is provided by the Marketo MCP Server MCP server (tyron-pretorius/marketo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Marketo MCP Server, and thousands of servers like it.
Across the catalogue