custom_delete_landing_page_content_section
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-delete-landing-page-content-section.md
What custom_delete_landing_page_content_section does on Marketo MCP Server
AI agents call custom_delete_landing_page_content_section 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_landing_page_content_section is rated Critical
The tool irreversibly deletes landing page content sections, which cannot be undone. This is a destructive operation affecting marketing collateral. While not as critical as financial impact, the high confidence in destructive capability and potential business impact of losing landing page content justifies 'high' severity.
From the tool's definition Tool name contains 'delete' and operates on landing page content sections via Marketo REST API. The description indicates direct API calls that perform deletion operations on marketing assets.
Attacks that exploit this kind of access
The rule that runs custom_delete_landing_page_content_section 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_landing_page_content_section, this is the rule to start with:
custom_delete_landing_page_content_section 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_landing_page_content_section call is checked against it from then on.
Questions about custom_delete_landing_page_content_section
[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_landing_page_content_section: 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_landing_page_content_section 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_landing_page_content_section 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_landing_page_content_section. 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_landing_page_content_section 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