custom_clone_landing_page
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-clone-landing-page.md
What custom_clone_landing_page does on Marketo MCP Server
AI agents use custom_clone_landing_page to create or update resources in Marketo MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marketo MCP Server environment.
Why custom_clone_landing_page is rated Medium
Cloning a landing page creates a new asset (a copy), which is a Write operation. However, the description is nearly uninformative beyond 'calls the Marketo REST API directly,' so confidence is reduced. Severity is high because misuse could proliferate landing pages at scale, potentially affecting marketing campaigns and brand presence. No evidence of destructive, financial, or execute behavior is present.
From the tool's definition 'clone_landing_page' implies creating a copy of an existing landing page, which is a write/create operation. The description notes it 'Calls the Marketo REST API directly' but provides no further detail about what the clone operation does.
Attacks that exploit this kind of access
The rule that runs custom_clone_landing_page 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_clone_landing_page, this is the rule to start with:
custom_clone_landing_page stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every custom_clone_landing_page call is checked against it from then on.
Questions about custom_clone_landing_page
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Write tool in the Marketo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_clone_landing_page: 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_clone_landing_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the custom_clone_landing_page 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_clone_landing_page. 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_clone_landing_page 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.
This server
Across the catalogue