custom_discard_landing_page_template_draft
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-discard-landing-page-template-draft.md
What custom_discard_landing_page_template_draft does on Marketo MCP Server
AI agents call custom_discard_landing_page_template_draft 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_discard_landing_page_template_draft is rated Critical
The verb 'discard' typically means to permanently remove or abandon without recovery. In a marketing automation context like Marketo, discarding a draft template state is an irreversible operation that cannot be undone—the draft changes are lost. This fits the Destructive category (irreversibly deletes or overwrites data). While not deleting the template entirely, it destroys the draft version's work.
From the tool's definition Tool name includes 'discard', which indicates removal or deletion. 'draft' suggests the action targets a specific version. Combined with 'landing_page_template', this tool appears to irreversibly discard a draft state of a template asset.
Attacks that exploit this kind of access
The rule that runs custom_discard_landing_page_template_draft 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_discard_landing_page_template_draft, this is the rule to start with:
custom_discard_landing_page_template_draft 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_discard_landing_page_template_draft call is checked against it from then on.
Questions about custom_discard_landing_page_template_draft
[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_discard_landing_page_template_draft: 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_discard_landing_page_template_draft 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_discard_landing_page_template_draft 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_discard_landing_page_template_draft. 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_discard_landing_page_template_draft 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