custom_approve_email_template · Marketo MCP Server MCP

WHAT IT DOES

What custom_approve_email_template does on Marketo MCP Server

AI agents use custom_approve_email_template 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_approve_email_template needs a policy

Approving an email template changes its status from draft/pending to approved, enabling it for use in campaigns. This is a reversible modification (templates can be unapproved or re-edited), not destructive. However, severity is high because approving templates can directly enable delivery of marketing content to audiences, and misuse could result in unauthorized or harmful emails being sent to large contact lists.

From the tool's definition Tool name contains 'approve' and 'email_template'; description indicates it calls Marketo REST API to approve email templates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_approve_email_template Rate-limited

custom_approve_email_template 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_approve_email_template": {
      "limits": [
        {
          "counter": "custom_approve_email_template_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_approve_email_template

What does the custom_approve_email_template 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_approve_email_template? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_approve_email_template: 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_approve_email_template? +

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

Can I rate-limit custom_approve_email_template? +

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

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

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