custom_clone_email · Marketo MCP Server MCP: Risk & Policy

WHAT IT DOES

What custom_clone_email does on Marketo MCP Server

AI agents use custom_clone_email 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 IT NEEDS A POLICY

Why custom_clone_email needs a policy

Cloning an email in Marketo creates a new copy of an existing email asset, which is a Write operation (creating new data reversibly). The 'custom' prefix and vague description ('Calls the Marketo REST API directly') lower confidence slightly, but the name strongly implies a clone/copy action analogous to sibling tools like clone_program and clone_smart_campaign.

From the tool's definition Tool name 'custom_clone_email' combined with server description mentioning 'comprehensive management of Marketo assets including emails'. The description states it 'Calls the Marketo REST API directly'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_clone_email Rate-limited

custom_clone_email 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_clone_email": {
      "limits": [
        {
          "counter": "custom_clone_email_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Marketo MCP Server, so you can run agents against it safely.

FAQ

Questions about custom_clone_email

What does the custom_clone_email tool do? +

[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.

How do I enforce a policy on custom_clone_email? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_clone_email: 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.

What risk level is custom_clone_email? +

custom_clone_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit custom_clone_email? +

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

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

custom_clone_email 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.