custom_transition_email2_state · Marketo MCP Server MCP

WHAT IT DOES

What custom_transition_email2_state does on Marketo MCP Server

AI agents invoke custom_transition_email2_state to trigger actions in Marketo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why custom_transition_email2_state needs a policy

This tool directly calls the Marketo REST API to perform a state transition on an email object. State transitions (e.g., draft → approved, approved → unapproved) are operational changes that can trigger campaign executions or affect live marketing assets. The 'custom' prefix and 'direct API call' description indicate arbitrary execution potential beyond standard read/write, placing it in Execute.

From the tool's definition 'Calls the Marketo REST API directly' and the name 'custom_transition_email2_state' suggests triggering a state transition on an email asset

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_transition_email2_state Rate-limited

custom_transition_email2_state stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_transition_email2_state": {
      "limits": [
        {
          "counter": "custom_transition_email2_state_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_transition_email2_state

What does the custom_transition_email2_state tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Execute tool in the Marketo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on custom_transition_email2_state? +

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

custom_transition_email2_state is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit custom_transition_email2_state? +

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

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

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